> OK, we need to vote on whether Oid's are optional, > and whether we can have them not created by default. Optional OIDs: YES No OIDs by default: YES > > > 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. So, add class' ID (uniq id from pg_class) when linking. Vadim ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Larry Rosenman
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Bruce Momjian
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Bruce Momjian
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Bruce Momjian
- RE: OID wraparound (was Re: [HACKERS] pg_depend) Mikheev, Vadim
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Bruce Momjian
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Tom Lane
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Mikheev, Vadim
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Larry Rosenman
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Lamar Owen
- [HACKERS] Re: OID wraparound (was Re: pg_depend) [EMAIL PROTECTED]
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Tom Lane
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Bruce Momjian
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Ross J. Reedstrom
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Tom Lane
- Re: OID wraparound (was Re: [HACKERS] pg_depend) Tom Lane