From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | nk(dot)schjoedt(at)gmail(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #9895: Duplicate pkey |
Date: | 2014-04-08 00:22:12 |
Message-ID: | CAB7nPqTgyKmZBKz2iMjO9-X3OXMdgekFyE_ZvP8BWBwpRm5SXQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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
From | Date | Subject | |
---|---|---|---|
Next Message | bricklen | 2014-04-08 01:00:05 | Re: BUG #9898: WindowAgg's causing horrific plans |
Previous Message | fburgess | 2014-04-07 22:25:14 | Re: Configuring Standby Server in PostgreSQL 9.3.3 |