Re: Re: OID wraparound: summary and proposal - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Re: OID wraparound: summary and proposal
Date
Msg-id 3B69C55F.CFC06DF5@tm.ee
Whole thread Raw
In response to OID wraparound: summary and proposal  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
mlw wrote:
> 
> I posted this question earlier, but it looks like it never made it on.
> 
> If you can control the OIDs on a per table basis, and some tables need not even
> have any, why not let each table have its own OID range? Essentially, each
> record will be numbered relative to 0 on its table?
> 
> That would really cut down the OID wrap around problem, and allow records to
> have a notion of serialization.
What would the meaning of such an "OID" be ?

Apart from duplicating the primary key that is ?

------------------
Hannu


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Rules for updatable views (was Re: [PATCHES] Revised Patch to allow multiple table locks in "Unison")
Next
From: Tom Lane
Date:
Subject: Re: Re: OID wraparound: summary and proposal