SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-11-2008, 06:03 AM
| ||||
| ||||
 Syntax of transaction identifiers Why are the transaction identifiers used in the 2PC commands lexical strings rather than identifiers? Shouldn't database objects be identifiers and strings be purely data objects? Or is there some standard or precedent on that? -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org      |
|
04-11-2008, 06:03 AM
| ||||
| ||||
| Re: Syntax of transaction identifiers Peter Eisentraut <peter_e@gmx.net> writes: > Why are the transaction identifiers used in the 2PC commands lexical > strings rather than identifiers? Shouldn't database objects be > identifiers and strings be purely data objects? Or is there some > standard or precedent on that? I proposed the same awhile back, but it was shot down --- there is a standard out there somewhere, and it requires strings of 150 or so characters for GIDs, so identifiers don't work. See the archives. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
Linear Mode
