Re: pg_restore duplicate key violations - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_restore duplicate key violations
Date
Msg-id 11859.1147188268@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_restore duplicate key violations  ("Karl O. Pinc" <kop@meme.com>)
Responses Re: pg_restore duplicate key violations  ("Karl O. Pinc" <kop@meme.com>)
List pgsql-general
"Karl O. Pinc" <kop@meme.com> writes:
> On 05/08/2006 06:42:18 PM, Tom Lane wrote:
>> Um ... it looks to me like you're trying to restore into an existing
>> table that already has the same data loaded ...

> That's what I thought at first, except that I had just created
> the db structure with a script.  Just in case I checked with
> a select from psql.  I even looked at the dump (as text) output to
> check that it wasn't doing something wierd like loading things
> twice.  Turns out this table is the first to have data loaded into
> it.

> I'm not clear on where to start with this.

Well, the first thing is to look at the database after the failure and
see if there's already data in the table.  I'm betting you'll find there
is.  Then you would start trying to figure out where it came from.

One thought that comes to mind: maybe the table exists in template1?

            regards, tom lane

pgsql-general by date:

Previous
From: Ryan Suarez
Date:
Subject: Exporting postgres query to CSV
Next
From: "Karl O. Pinc"
Date:
Subject: Re: pg_restore duplicate key violations