From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_restore duplicate key violations |
Date: | 2006-05-09 15:24:28 |
Message-ID: | 11859.1147188268@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Karl O. Pinc" <kop(at)meme(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Karl O. Pinc | 2006-05-09 15:31:34 | Re: pg_restore duplicate key violations |
Previous Message | Karl O. Pinc | 2006-05-09 15:20:13 | Re: pg_restore duplicate key violations |