RE: OID wraparound (was Re: pg_depend) - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: OID wraparound (was Re: pg_depend)
Date
Msg-id 3705826352029646A3E91C53F7189E320166D7@sectorbase2.sectorbase.com
Whole thread Raw
In response to OID wraparound (was Re: pg_depend)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: OID wraparound (was Re: pg_depend)
List pgsql-hackers
> 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 -:)

> 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.

There is no magic around OIDs.

Vadim


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: OID wraparound (was Re: pg_depend)
Next
From: Bruce Momjian
Date:
Subject: Re: OID wraparound (was Re: pg_depend)