On 05/08/2006 06:42:18 PM, Tom Lane wrote:
"Karl O. Pinc" <[EMAIL PROTECTED]> writes:
> I'm having trouble with a dump and restore:
> $ pg_dump --format=t --schema=babase --data-only --user babase_admin
> babase_test | pg_restore --data-only --disable-triggers --user
> babase_admin --dbname=babase
> pg_restore: ERROR: duplicate key violates unique constraint
> "activities_pkey"
> CONTEXT: COPY activities, line 1: "B t t Be groomed"
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.
Karl <[EMAIL PROTECTED]>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
