X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id B9CB8D1B3CE for ; Tue, 11 May 2004 12:11:53 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 33401-04 for ; Tue, 11 May 2004 12:11:32 -0300 (ADT) Received: from yapok.nexcerpt.com (mail.nexcerpt.com [64.147.202.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2B536D1B347 for ; Tue, 11 May 2004 12:11:26 -0300 (ADT) Received: from nexcerpt.com (zorro.nexcerpt.com [64.147.202.1]) by yapok.nexcerpt.com (8.12.8/8.12.8) with ESMTP id i4BFBEP1006230 for ; Tue, 11 May 2004 11:11:14 -0400 Message-ID: <40A0ED12.70101@nexcerpt.com> Date: Tue, 11 May 2004 11:11:14 -0400 From: Jeff Boes Organization: Nexcerpt, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040421 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: OID Overflow for large objects References: <4cb583f0740a5ee302887ff58f59665d@news.teranews.com> <15078.1083956932@sss.pgh.pa.us> In-Reply-To: <15078.1083956932@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/82 X-Sequence-Number: 13398 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