From: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_restore duplicate key violations |
Date: | 2006-05-09 15:31:34 |
Message-ID: | 1147188694l.18374l.7l@mofo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/09/2006 10:24:28 AM, Tom Lane wrote:
> "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 ...
>
> > 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.
I tried that already. Nothing in the table.
>
> One thought that comes to mind: maybe the table exists in template1?
Don't think so. Nothing has gone into template1.
Karl <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Armbrust | 2006-05-09 15:39:30 | Problem dropping a table |
Previous Message | Tom Lane | 2006-05-09 15:24:28 | Re: pg_restore duplicate key violations |