pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeff Boes <jboes@nexcerpt.com>
To: pgsql-admin@postgresql.org
Subject: Re: OID Overflow for large objects
Date: Tue, 11 May 2004 11:11:14 -0400
Message-ID: <40A0ED12.70101@nexcerpt.com> (raw)
In-Reply-To: <15078.1083956932@sss.pgh.pa.us>
References: <4cb583f0740a5ee302887ff58f59665d@news.teranews.com>
	<15078.1083956932@sss.pgh.pa.us>

Tom Lane wrote:

>>(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.
>
>	
>

Pardon my incredulity, but doesn't that seem like a bug? Or at least a 
limitation? Does this mean that the effective useful lifetime of 
pg_largeobject is only as long as it takes to wrap around, after which 
you *must* dump and reload to prevent problems like this?

(I realize this is pretty much the same issue as having a sequence 
number on a table, but if I'm interpreting all this correctly, the OID 
wrap-around is going to occur a lot sooner than my table sequence number 
wrap-around.)


-- 
Jeff Boes                                      vox 269.226.9550 ext 24
Database Engineer                                     fax 269.349.9076
Nexcerpt, Inc.                                 http://www.nexcerpt.com
           ...Nexcerpt... Extend your Expertise




view thread (3+ messages)

Message-ID: <40A0ED12.70101@nexcerpt.com>
Permalink:  ../40A0ED12.70101@nexcerpt.com/
Also on:    postgresql.org/message-id/40A0ED12.70101@nexcerpt.com

 · 

reply

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: jboes@nexcerpt.com
  Subject: Re: OID Overflow for large objects
  In-Reply-To: <40A0ED12.70101@nexcerpt.com>
  References: <4cb583f0740a5ee302887ff58f59665d@news.teranews.com> <15078.1083956932@sss.pgh.pa.us> <40A0ED12.70101@nexcerpt.com>

* 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