Re: Duplicate Key violation on dump&reload using pg_restore - Mailing list pgsql-general

From Markus Wollny
Subject Re: Duplicate Key violation on dump&reload using pg_restore
Date
Msg-id 28011CD60FB1724DBA4442E38277F62607CD83D6@hermes.computec.de
Whole thread Raw
In response to Duplicate Key violation on dump&reload using pg_restore  ("Markus Wollny" <Markus.Wollny@computec.de>)
List pgsql-general
Quick update: Seems like removing that tuple has solved the issue, dump and import of that table went fine, everything is where is should be - but there shouldn't have been an issue there in the first place however, with the primary key constraint present in the source database. I'm still curious, even though I've now got less to worry about the upcoming migration :)


Computec Media AG

Sitz der Gesellschaft und Registergericht: Fürth (HRB 8818)

Vorstandsmitglieder: Johannes S. Gözalan (Vorsitzender) und Rainer Rosenbusch

Vorsitzender des Aufsichtsrates: Jürg Marquard

Umsatzsteuer-Identifikationsnummer: DE 812 575 276

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Duplicate Key violation on dump&reload using pg_restore
Next
From: "Markus Wollny"
Date:
Subject: Re: Duplicate Key violation on dump&reload using pg_restore