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 18:12:39 |
Message-ID: | 1147198359l.18374l.13l@mofo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/08/2006 06:42:18 PM, Tom Lane wrote:
> "Karl O. Pinc" <kop(at)meme(dot)com> writes:
> > I'm having trouble with a dump and restore:
>
> Um ... it looks to me like you're trying to restore into an existing
> table that already has the same data loaded ...
Thanks everybody, the problem was in the schemas and my default
search path. Somehow when upgrading to 8.1.3 I wound up with
the public schema put back into all my databases, and my
search paths of the databases set back to the default $user,public.
I can see how the public schema got there, this time I did not
delete the public schema from template1. I'm not so sure about
the search path. Obviously, I did not do my pg_restore properly
when reloading databases.
Karl <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2006-05-09 18:25:27 | Re: [PERFORM] Arguments Pro/Contra Software Raid |
Previous Message | Douglas McNaught | 2006-05-09 18:05:28 | Re: Arguments Pro/Contra Software Raid |