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

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "mlw" <markw(at)mohawksoft(dot)com>
Cc: "Hannu Krosing" <hannu(at)tm(dot)ee>, <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: AW: Re: OID wraparound: summary and proposal
Date: 2001-08-06 12:17:21
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA4212711@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 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.
A lot of people seem to use OID, when they really could use XTID. That
is
what I wanted to say.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Pilosov 2001-08-06 12:29:05 Re: AW: Re: OID wraparound: summary and proposal
Previous Message Rene Pijlman 2001-08-06 11:44:29 Re: Vim!