Re: AW: Re: OID wraparound: summary and proposal

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>
Cc: mlw <markw(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: AW: Re: OID wraparound: summary and proposal
Date: 2001-08-06 14:50:47
Message-ID: 3B6EAEC7.A9630CD9@tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zeugswetter Andreas SB SD wrote:
>
> > It seems to me, I guess and others too, that the OID mechanism should
> be on a
> > per table basis. That way OIDs are much more likely to be unique, and
> TRUNCATE
> > on a table should reset it's OID counter to zero.
>
> Seems to me, that this would be no different than a performance improved
> version
> of SERIAL.
> If you really need OID, you imho want the systemid tableid tupleid
> combo.

or (systemid.tableid.tupleid.versioninterval) if you want to be able to
time-travel

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-08-06 14:53:20 Re: Question about todo item
Previous Message Hannu Krosing 2001-08-06 14:48:15 Re: Re: AW: Re: OID wraparound: summary and proposal