Re: ERROR: duplicate key value violates unique constraint "geocode_settings_pkey"

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "'Ankur Kaushik *EXTERN*'" <ankurkaushik(at)gmail(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: ERROR: duplicate key value violates unique constraint "geocode_settings_pkey"
Date: 2015-06-15 16:01:13
Message-ID: A737B7A37273E048B164557ADEF4A58B50F625DF@ntex2010a.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Kiswono Prayogo 2015-06-16 08:10:28 Slow when joining with view
Previous Message Albe Laurenz 2015-06-15 15:59:31 Re: ERROR: duplicate key value violates unique constraint "geocode_settings_pkey"