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 776A5D1EDE9 for ; Fri, 7 May 2004 16:09:15 -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 02660-01 for ; Fri, 7 May 2004 16:08:56 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id D296AD1ED5A for ; Fri, 7 May 2004 16:08:54 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i47J8qWM015079; Fri, 7 May 2004 15:08:52 -0400 (EDT) To: jboes@nexcerpt.com Cc: pgsql-admin@postgresql.org, Bruce Momjian Subject: Re: OID Overflow for large objects In-reply-to: <4cb583f0740a5ee302887ff58f59665d@news.teranews.com> References: <4cb583f0740a5ee302887ff58f59665d@news.teranews.com> Comments: In-reply-to Jeff Boes message dated "Fri, 07 May 2004 18:07:38 +0000" Date: Fri, 07 May 2004 15:08:52 -0400 Message-ID: <15078.1083956932@sss.pgh.pa.us> From: Tom Lane 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/70 X-Sequence-Number: 13386 Jeff Boes 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