Re: duplicate key value violates unique constraint and duplicated records

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Timokhin Maxim <ncx2(at)yandex(dot)com>, Melvin Davidson <melvin6925(at)gmail(dot)com>, stevenchang1213(at)gmail(dot)com
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: duplicate key value violates unique constraint and duplicated records
Date: 2017-06-30 13:07:00
Message-ID: f413d42a-018d-4adb-68d6-845ab5a711f1@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 06/30/2017 04:58 AM, Timokhin Maxim wrote:
> BTW, we are moving using:
>
> pg_basebackup -h servername -R -P -D /data/upgrade/94 -U pgsql -v —xlog-method=stream —checkpoint=fast

Going from 9.4 to 9.6 is a major version upgrade and you cannot use
pg_basebackup for that. Besides I can't see how you even got the 9.6.3
server to start:

/usr/local/pgsql94/bin/pg_basebackup -D /home/aklaver/pgback_test94 -U
postgres -p 5412 -v --xlog-method=stream

/usr/local/pgsql96/bin/pg_ctl -D /home/aklaver/pgback_test94/ start
server starting
FATAL: database files are incompatible with server
DETAIL: The data directory was initialized by PostgreSQL version 9.4,
which is not compatible with this version 9.6.3

>
> After that we are upping version to 9.6.3.

Given the above how did you actually get 9.6.3 to start?

> I've looked through the documentation https://postgrespro.ru/docs/postgrespro/9.6/app-pgbasebackup and didn't find details about how pg_basebackup works with b-tree indexes.
> Is it possible that pg_basebackup just copies indexes as is and that is cause of corruption. Or it pass indexes as instruction that says "after upping db make indexes" ?
>
> Thank you.
>
>
> --
> Timokhin 'maf' Maxim
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Melvin Davidson 2017-06-30 13:28:02 Re: duplicate key value violates unique constraint and duplicated records
Previous Message Mikhail 2017-06-30 12:35:25 Re: [GENERAL] Significant discrepancy in index cost estimation