X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D6EA99FA5E7; Fri, 9 Jun 2006 12:18:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 47460-08; Fri, 9 Jun 2006 12:18:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 96A449FA098; Fri, 9 Jun 2006 12:18:30 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k59FIN1K010906; Fri, 9 Jun 2006 11:18:23 -0400 (EDT) To: =?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= cc: Alvaro Herrera , pgsql-admin@postgresql.org, pgsql-general@postgresql.org, pgsql-bugs@postgresql.org, Sven Geisler , pavel rabaev Subject: Re: How to set the global OID counter? COPY WITH OIDS does In-reply-to: <4489887D.6080505@aeccom.com> References: <448976E3.50209@aeccom.com> <20060609140015.GF19659@surnet.cl> <9780.1149863199@sss.pgh.pa.us> <4489887D.6080505@aeccom.com> Comments: In-reply-to =?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= message dated "Fri, 09 Jun 2006 16:41:01 +0200" Date: Fri, 09 Jun 2006 11:18:23 -0400 Message-ID: <10905.1149866303@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/74 X-Sequence-Number: 22036 =?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= writes: > This is not a large object. We are seeing rows with duplicate oids > because the OID counter is not changed after the dump (exported with > --oids) is being loaded. > How does 8.1 prevent to allocate duplicate OIDs? If there's a unique index on the OID column then 8.1 will not allocate duplicate OIDs. If there's not such a unique index, you had no guarantee of no-duplicates before 8.1 either. regards, tom lane