BUG #13862: Duplicated rows for a table with primary key

On Wed, Jan 13, 2016 at 9:51 AM, <y.chaitanya@tcs.com> wrote:

The following bug has been logged on the website:

Bug reference: 13862
Logged by: krishna chaitanya
Email address: y.chaitanya@tcs.com
PostgreSQL version: 9.1.2
Operating system: SUSE Linux E nterprise Server 11 SP2
Description:

we have an issue in production server where the tables with primary key
constraint are duplicated. Complete row is duplicated with identical
values
.

So please help us to know the root cause for this. We are able to delete
the
duplicates, but not sure what cause this issue

You are going to have to provide more information​ than this.

You are also using an ancient 9.1 release; 9.1.19 is current.

David J.

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.

Details:
Table description as below with network_element_pk column having primary
key.

Due to some reason, may be due to large transactions, (frequently) the
rows got duplicated as below, Let me know if you need any more details.

Best Regards
Krishna Chaitanya
Tata Consultancy Services
Mailto: y.chaitanya@tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

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 12:57 AM
Subject: Re: [BUGS] BUG #13862: Duplicated rows for a table with
primary key

On Wed, Jan 13, 2016 at 9:51 AM, <y.chaitanya@tcs.com> wrote:
The following bug has been logged on the website:

Bug reference: 13862
Logged by: krishna chaitanya
Email address: y.chaitanya@tcs.com
PostgreSQL version: 9.1.2
Operating system: SUSE Linux E nterprise Server 11 SP2
Description:

we have an issue in production server where the tables with primary key
constraint are duplicated. Complete row is duplicated with identical
values
.

So please help us to know the root cause for this. We are able to delete
the
duplicates, but not sure what cause this issue

You are going to have to provide more information​ than this.

You are also using an ancient 9.1 release; 9.1.19 is current.

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

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.

Details:
Table description as below with network_element_pk column having primary
key.

Due to some reason, may be due to large transactions, (frequently) the
rows got duplicated as below, Let me know if you need any more details.

Best Regards
Krishna Chaitanya
Tata Consultancy Services
Mailto: y.chaitanya@tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

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 12:57 AM
Subject: Re: [BUGS] BUG #13862: Duplicated rows for a table with
primary key

On Wed, Jan 13, 2016 at 9:51 AM, <y.chaitanya@tcs.com> wrote:
The following bug has been logged on the website:

Bug reference: 13862
Logged by: krishna chaitanya
Email address: y.chaitanya@tcs.com
PostgreSQL version: 9.1.2
Operating system: SUSE Linux E nterprise Server 11 SP2
Description:

we have an issue in production server where the tables with primary key
constraint are duplicated. Complete row is duplicated with identical
values
.

So please help us to know the root cause for this. We are able to delete
the
duplicates, but not sure what cause this issue

You are going to have to provide more information​ than this.

You are also using an ancient 9.1 release; 9.1.19 is current.

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

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.

Details:
Table description as below with network_element_pk column having primary
key.

Due to some reason, may be due to large transactions, (frequently) the
rows got duplicated as below, Let me know if you need any more details.

Best Regards
Krishna Chaitanya
Tata Consultancy Services
Mailto: y.chaitanya@tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

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 12:57 AM
Subject: Re: [BUGS] BUG #13862: Duplicated rows for a table with
primary key

On Wed, Jan 13, 2016 at 9:51 AM, <y.chaitanya@tcs.com> wrote:
The following bug has been logged on the website:

Bug reference: 13862
Logged by: krishna chaitanya
Email address: y.chaitanya@tcs.com
PostgreSQL version: 9.1.2
Operating system: SUSE Linux E nterprise Server 11 SP2
Description:

we have an issue in production server where the tables with primary key
constraint are duplicated. Complete row is duplicated with identical
values
.

So please help us to know the root cause for this. We are able to delete
the
duplicates, but not sure what cause this issue

You are going to have to provide more information​ than this.

You are also using an ancient 9.1 release; 9.1.19 is current.

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

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.

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

On Thu, Jan 14, 2016 at 8:50 AM, <y.chaitanya@tcs.com> wrote:

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
<http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b994c57a8032f55f816768ee55a677e03190abae&gt;

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.

​I doubt that your problem is related..

​David J.​

HI David,

Thanks for your time,

For us , the basic primary key feature is violated, So there must be
some reason for this, Please let me know if you need any other
information for finding the root cause.
Also some advice to avoid this will be helpful.

Best 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 09:49 PM
Subject: Re: [BUGS] BUG #13862: Duplicated rows for a table with
primary key

On Thu, Jan 14, 2016 at 8:50 AM, <y.chaitanya@tcs.com> wrote:
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.

​I doubt that your problem is related..

​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

On Fri, Jan 15, 2016 at 1:56 AM, <y.chaitanya@tcs.com> wrote:

HI David,

Thanks for your time,

For us , the basic primary key feature is violated, So there must be
some reason for this, Please let me know if you need any other information
for finding the root cause.
Also some advice to avoid this will be helpful.

​I neither have the time nor expertise to play email technical support for
an issue like this. Upgrade to the newest patch release, remove the
duplicates, and reindex. If the problem recurs turn on detailed logging
and try to isolate the process and related queries that is introducing the
duplicates.

​Or just wait around and see if someone else wants to pick up torch and
help you for free.

Or contact a professional services company and pay someone to do the same.

The community does take pride in the quality of its software but if you
cannot provide a re-producible test case on the most recent release of
PostgreSQL no one is going to be able to fix the problem should one even
exist. It is most likely assumed to either already have been fixed in a
more recent release or the cause is isolated to something that is unique to
your situation or a transient issue that can be cleared up using the tools
(e.g., reindex) provided.

David J.

On Fri, Jan 15, 2016 at 5:26 PM, David G. Johnston <
david.g.johnston@gmail.com> wrote:

On Fri, Jan 15, 2016 at 1:56 AM, <y.chaitanya@tcs.com> wrote:

HI David,

Thanks for your time,

For us , the basic primary key feature is violated, So there must be
some reason for this, Please let me know if you need any other information
for finding the root cause.
Also some advice to avoid this will be helpful.

​I neither have the time nor expertise to play email technical support for
an issue like this.

More specifically, OP please take some time to follow this guide:
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems

--
Alex