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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-bugs by date

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