Re: BUG #9895: Duplicate pkey

From: Niels Kristian Schjødt <nk(dot)schjoedt(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #9895: Duplicate pkey
Date: 2014-04-08 08:02:46
Message-ID: 838D1286-4D43-472F-B26A-55284523577D@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 -> checking again, to make sure that my data is OK?

Den 08/04/2014 kl. 02.22 skrev Michael Paquier <michael(dot)paquier(at)gmail(dot)com>:

> On Mon, Apr 7, 2014 at 8:57 PM, <nk(dot)schjoedt(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Sofer, Yuval 2014-04-08 10:12:16 Re: Postgres 9.2.8 crash sporadically on Windows
Previous Message Gayathri Manoj 2014-04-08 04:36:19 Re: BUG #9894: SQLError() is not returns SQL_NO_DATA_FOUND