Re: OID's....

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Steve Wolfe <steve(at)iboats(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: OID's....
Date: 2001-05-30 21:47:36
Message-ID: 200105302147.f4ULlaH09463@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> > Also, when the OID's reach the limit of an int4, if I recall correctly,
> > they simply wrap around, and things keep working unless you depend on
> > unique OID's. Is that correct?
>
> That's the theory, anyway. After the wrap, you could see occasional
> failures due to OID conflicts in the system catalogs --- for example, if
> you try to create a table but the assigned OID duplicates some existing
> table's OID, you'd get a can't-insert-duplicate-into-unique-index kind
> of failure. The solution if that happens is just to try again;
> eventually you'll get an OID that doesn't conflict. But the odds of a
> conflict like that should be very low in practice.

Seems we could avoid that by getting another oid and retrying.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-general by date

  From Date Subject
Next Message rui zhong 2001-05-30 23:08:59 Does ASSERTION constraint work ?
Previous Message HYip 2001-05-30 21:33:22 timeout for a transaction