Обсуждение: ERROR: duplicate key value violates unique constraint "geocode_settings_pkey"

Ankur Kaushik wrote:
> I took Backup using below command
>  pg_dump "database name" | gzip > /root/dump.sql.gz
>
>
>
> While restoring in fresh PostgreSQL  server getting below error .
>
> ERROR:  duplicate key value violates unique constraint "geocode_settings_pkey"
> DETAIL:  Key (name)=(debug_geocode_address) already exists.

That looks like data corruption on the original database.

Look at https://wiki.postgresql.org/wiki/Corruption and
follow the "VITALLY IMPORTANT FIRST RESPONSE".

Check if that is the only row that violates the constraint.
You could manually delete all offending rows on the source,
then dump/restore (don't continue working with the database
even if it seems consistent again).

Yours,
Laurenz Albe

I opened the Backup File seen , The duplicate error came in schema : tiger , table : geocode_setting , already data for primary key column exist "debug_geocode_address" primary key value

What is use of tiger schema , is related postGIS . Can we take dump for only schema public ?

On Mon, Jun 15, 2015 at 3:27 PM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:

Ankur Kaushik wrote:
> I took Backup using below command
>  pg_dump "database name" | gzip > /root/dump.sql.gz
>
>
>
> While restoring in fresh PostgreSQL  server getting below error .
>
> ERROR:  duplicate key value violates unique constraint "geocode_settings_pkey"
> DETAIL:  Key (name)=(debug_geocode_address) already exists.

That looks like data corruption on the original database.

Look at https://wiki.postgresql.org/wiki/Corruption and
follow the "VITALLY IMPORTANT FIRST RESPONSE".

Check if that is the only row that violates the constraint.
You could manually delete all offending rows on the source,
then dump/restore (don't continue working with the database
even if it seems consistent again).

Yours,
Laurenz Albe

Ankur Kaushik wrote:
> I think this is not a database corrupt , While create a new database there is already Entry in
> geocode_setting  tiger schema . Correct me If I am Wrong .

Well, you wrote that you were restoring to a "fresh database server", so I was assuming
that the database was empty.

Preexisting data can of course also lead to this problem.

Yours,
Laurenz Albe

Ankur Kaushik wrote:
> So is there any way to restore database without any error , or Can we put one line in database backup
> file , DROP TABLE 'table name' just before CREATE TABLE.

You mean like the -c option in pg_dump or pg_restore?

Yours,
Laurenz Albe