> > If you want to make oids optional on user tables,
> > we can vote on that.
>
> Let's vote. I'm proposing optional oids for 2-3 years,
> so you know how I'll vote -:)
OK, we need to vote on whether Oid's are optional, and whether we can
have them not created by default.
>
> > However, OID's keep our system tables together.
>
> How?! If we want to find function with oid X we query
> pg_proc, if we want to find table with oid Y we query
> pg_class - we always use oids in context of "class"
> to what an object belongs. This means that two tuples
> from different system tables could have same oid values
> and everything would work perfectly.
I meant we use them in many cases to link entries, and in pg_description
for descriptions and lots of other things that may use them in the
future for system table use.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
