Skip site navigation (1) Skip section navigation (2)

Re: BUG #3110: Online Backup introduces Duplicate OIDs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Randy Isbell" <jisbell(at)cisco(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3110: Online Backup introduces Duplicate OIDs
Date: 2007-03-06 17:43:47
Message-ID: 6282.1173203027@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Randy Isbell" <jisbell(at)cisco(dot)com> writes:
> When restoring the output of an online backup, many tables now have
> duplicate OID values / primary keys, viz:
> ...
> sn=# reindex table at_dns;
> ERROR:  could not create unique index

I'm confused.  You're claiming that the reload succeeds, but after that
a reindex fails?  Are there actually duplicate OIDs in the dump file,
as evidenced by looking at it?  What pg_dump options are you using
(I suppose -o at least)?  If using pg_restore, what options there?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2007-03-06 17:55:55
Subject: Re: BUG #3113: pg_restore --use-list=FILENAME
Previous:From: Kris JurkaDate: 2007-03-06 16:49:05
Subject: Re: BUG #3106: A problem with escaping table name pattern for DatabaseMetaData.getColumns()

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group