HI David,
For us the problem occurred in postgresql 9.1.2 and in release notes for
9.1.3 found below link:
pgsql: Fix CLUSTER/VACUUM FULL for toast values owned byrecently-updat
So can you please confirm if the primary key violation is due the bug
mentioned in the above fix.?
If you need any other information ,other than screen shot please let me
know.
Thanks& Regards
Krishna Chaitanya
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: y.chaitanya@tcs.com
Cc: "pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.org>
Date: 14-01-16 08:53 PM
Subject: Re: [BUGS] BUG #13862: Duplicated rows for a table with
primary key
On Thu, Jan 14, 2016 at 5:18 AM, <y.chaitanya@tcs.com> wrote:
From: Y Chaitanya/CHN/TCS
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: "pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.org>
Date: 14-01-16 04:27 PM
Subject: Re: [BUGS] BUG #13862: Duplicated rows for a table with
primary key
HI David,
Thanks for the reply,
Yes I agree that it is old version, But can you let us know if there are
any old bugs that violates the primary key.
This is why we have release notes.
If nothing there gives you a clue then the two screenshots you've provided
are insufficient diagnostic - though they do indeed show that at some
point you had a problem.
A simple action to take is to remove all duplicates and then reindex. It
may be simple corruption at hand. It happens - usually due to hardware
issues.
David J.
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you