Re: ERROR: duplicate key value violates unique constraint "geocode_settings_pkey"
| От | Albe Laurenz |
|---|---|
| Тема | Re: ERROR: duplicate key value violates unique constraint "geocode_settings_pkey" |
| Дата | |
| Msg-id | A737B7A37273E048B164557ADEF4A58B50F5D01D@ntex2010a.host.magwien.gv.at обсуждение исходный текст |
| Ответ на | ERROR: duplicate key value violates unique constraint "geocode_settings_pkey" (Ankur Kaushik <ankurkaushik@gmail.com>) |
| Ответы |
Re: ERROR: duplicate key value violates unique constraint "geocode_settings_pkey"
|
| Список | pgsql-admin |
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
В списке pgsql-admin по дате отправления: