From: Tom Lane <tgl@sss.pgh.pa.us>
To: jboes@nexcerpt.com
Cc: pgsql-admin@postgresql.org, Bruce Momjian <pgman@candle.pha.pa.us>
Subject: Re: OID Overflow for large objects
Date: Fri, 07 May 2004 15:08:52 -0400
Message-ID: <15078.1083956932@sss.pgh.pa.us> (raw)
In-Reply-To: <4cb583f0740a5ee302887ff58f59665d@news.teranews.com>
References: <4cb583f0740a5ee302887ff58f59665d@news.teranews.com>
Jeff Boes <jboes@nexcerpt.com> writes:
> I found some indication of the problem referenced in the Pg FAQ
> (http://www3.sk.postgresql.org/docs/faqs/FAQ.html):
> OIDs are stored as 4-byte integers, and will overflow at 4 billion. No
> one has reported this ever happening, and we plan to have the limit
> removed before anyone does.
That comment in the FAQ seems quite out-of-date.
What will actually happen is that the OID generator will wrap around.
This will not bother Postgres particularly, but you may start having
occasional transaction failures due to duplicate OIDs --- for example,
I believe lo_create will fail if the OID it selects already exists in
pg_largeobject.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, jboes@nexcerpt.com, pgman@candle.pha.pa.us
Subject: Re: OID Overflow for large objects
In-Reply-To: <15078.1083956932@sss.pgh.pa.us>
References: <4cb583f0740a5ee302887ff58f59665d@news.teranews.com> <15078.1083956932@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox