Re: [ADMIN] How to set the global OID counter? COPY WITH OIDS does

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Dirk Lutzeb?ck <lutzeb(at)aeccom(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [ADMIN] How to set the global OID counter? COPY WITH OIDS does
Date: 2006-06-09 17:42:34
Message-ID: 20060609174234.GB45331@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-bugs pgsql-general

In the future, please don't send the same email to a bunch of pgsql
lists; one is almost always sufficient. (In this case, -admin OR
-general woulud have been best).

On Fri, Jun 09, 2006 at 05:27:47PM +0200, Dirk Lutzeb?ck wrote:
> True.
>
> Dirk
>
> Tom Lane wrote:
> >=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <lutzeb(at)aeccom(dot)com> 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
> >
>
> --
> /This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they are
> addressed. If you are not the intended recipient, you should not copy
> it, re-transmit it, use it or disclose its contents, but should return
> it to the sender immediately and delete your copy from your system.
> Thank you for your cooperation./
>
> *Dirk Lutzeb?ck* <lutzeb(at)aeccom(dot)com> Tel +49.30.5362.1635 Fax .1638
> CTO AEC/communications GmbH <http://www.aeccom.com>, Berlin, Germany
>

--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message louis gonzales 2006-06-09 20:05:47 Re: Database port changing issue
Previous Message Chris Hoover 2006-06-09 17:27:37 Major Problems with PostgreSQL Logs (8.1.3)

Browse pgsql-bugs by date

  From Date Subject
Next Message Martin Pitt 2006-06-10 16:01:07 Fwd: Bug#372115: Last security update of postgresql-contrib breaks database replication with DBMirror.pl
Previous Message Jim C. Nasby 2006-06-09 17:33:29 Re: statement stuck when the connection grew up to 45 or more

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2006-06-09 17:51:44 Re: State of Postgresql Replication?
Previous Message Jim C. Nasby 2006-06-09 17:38:49 Re: OID