Re: BUG #9895: Duplicate pkey - Mailing list pgsql-bugs

From Niels Kristian Schjødt
Subject Re: BUG #9895: Duplicate pkey
Date
Msg-id 838D1286-4D43-472F-B26A-55284523577D@gmail.com
Whole thread Raw
In response to Re: BUG #9895: Duplicate pkey  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
Thanks, that is most defiantly the case.

What is the best approach on doing a loop of re-checking of all my constraints (pkeys, fkeys) -> fixing issues ->
checkingagain, to make sure that my data is OK? 

Den 08/04/2014 kl. 02.22 skrev Michael Paquier <michael.paquier@gmail.com>:

> On Mon, Apr 7, 2014 at 8:57 PM,  <nk.schjoedt@gmail.com> wrote:
>> Hi I just realized that my data contains a few duplicate primary keys! There
>> has ALWAYS been a PRIMARY KEY constraint on those ID's. The affected records
>> might have been created while running a previous version of postgresql.
>
> 9.3.4 has fixed a data corruption issue in WAL replay that could
> create inconsistent query results when using an index on a standby.
> This could lead to violations of primary keys for example. Perhaps you
> have been bitten by that:
> http://www.postgresql.org/docs/devel/static/release-9-3-4.html
> When updating to 9.3.4 it is recommended to replace all the standbys
> by a new base backup after the update.
> Regards,
> --
> Michael




pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres 9.2.8 crash sporadically on Windows
Next
From: Gayathri Manoj
Date:
Subject: Re: BUG #9894: SQLError() is not returns SQL_NO_DATA_FOUND