RE: OID wraparound (was Re: pg_depend)
От | Mikheev, Vadim |
---|---|
Тема | RE: OID wraparound (was Re: pg_depend) |
Дата | |
Msg-id | 3705826352029646A3E91C53F7189E320166D9@sectorbase2.sectorbase.com обсуждение исходный текст |
Ответ на | OID wraparound (was Re: pg_depend) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: OID wraparound (was Re: pg_depend)
|
Список | pgsql-hackers |
> 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
В списке pgsql-hackers по дате отправления: