Re: Duplicate key violates unique constraint

From: Umesh Kirdat <umesh(dot)kirdat(at)yahoo(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Duplicate key violates unique constraint
Date: 2014-01-14 06:50:03
Message-ID: 1389682203.8942.YahooMailNeo@web193105.mail.sg3.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thank you Greg for the response.
 
Our management wants to know whether the bugs 8382 & 3231 & 7760 are fixed in 9.0.15 before we decide to upgrade from 9.0.4 version to 9.0.15.
 
It would be helpful to convience our customers who has reported the issue.
 
Thank you,
Umesh

On Saturday, 21 December 2013 6:42 AM, Greg Stark <stark(at)mit(dot)edu> wrote:

On Fri, Dec 20, 2013 at 11:38 AM, Umesh Kirdat <umesh(dot)kirdat(at)yahoo(dot)com> wrote:

> The Postgres version on which the issue was reported is 8.2.2
> We have upgraded our Postgres version to 9.0.4 in the current product
> release and I would like to know whether the issue in discussion is fixed in
> Postgres 9.0.4?

When there's any sort of, thankfully rare, corruption bug the symptom
which people first notice is often duplicate primary keys. So your
question is really whether 9.0.4 is free of any (known) corruption
bugs.

For what it's worth the current release for the
9.0 major version is
9.0 is 9.0.15. There are over 2 1/2 years of bug fixes between 9.0.4
and 9.0.15 including some corruption bugs which could possibly
introduce duplicate rows. Also including one major security fix for
CVE-2013-1899.

--
greg

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeevan Chalke 2014-01-14 07:24:18 Re: [BUGS] surprising to_timestamp behavior
Previous Message Tom Lane 2014-01-14 01:59:48 Re: Hot standby 9.2.6 -> 9.2.6 PANIC: WAL contains references to invalid pages