> There are basically two ways to attack the problem of a database-wide
> unique ID:
>
> * Use a single int8 sequence for the whole database;
>
> * Use the combination of table OID and row OID (or, perhaps, an int8
> sequence for the row identifier, if you need more than a billion or
> so rows in
"Kevin Field" <[EMAIL PROTECTED]> writes:
> Either way, are 64-bit OIDs planned within the next couple years?
No, they're not planned at all. That line of thought has pretty much
died off, to the point where OIDs in user tables are not just deprecated
but not there at all by default.
There are b
Hi everyone,
I just came across a thread in the pgsql archives from October 2000, and found
this post particularly interesting:
http://archives.postgresql.org/pgsql-sql/2000-10/msg00044.php
...because I had already been designing something similar but on a larger
scale, for an integrated infor
