BUG #8891: Duplicate Primary Key
The following bug has been logged on the website:
Bug reference: 8891
Logged by: Anjali Arora
Email address: anjali_524@yahoo.co.in
PostgreSQL version: 8.4.0
Operating system: CentOS 5
Description:
Hi all,
I have been using pg_dump/pg_restore to backup and restore the database in
our product for quite sometime.
One of our customers reported an issue with multiple entries for a field
marked as primary key.
After investigation of the logs we found the multiple entires were created
during pg_restore and the primary key constraint on the field could not be
created due to unique constraint violation.
Even on internet I came across the Postgres BUG 8382 & 7760 reported in the
past for this issue.
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 verified the issue fix information into postgres release notes
9.0.4, 9.0.15, and 9.1 but could not find anything related to this issue.
Please let me know in which release this issue got fixed.
Thanks,
Anjali
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Mon, Jan 20, 2014 at 11:22 AM, <anjali_524@yahoo.co.in> wrote:
The Postgres version on which the issue was reported is 8.2.2
Do you realize that this version was released almost 7 years ago? The
last bugfix release in the 8.2 series was 8.2.23, only 2 years ago. If
you don't apply bugfixes then you *will* eventually hit bugs.
I verified the issue fix information into postgres release notes
9.0.4, 9.0.15, and 9.1 but could not find anything related to this issue.
It was probably some sort of index corruption, which allowed duplicate
values to be inserted. There have been a dozen bugs of this kind fixed
and it's hard to tell which one.
We have upgraded our Postgres version to 9.0.4
Wait, what? 9.0.15 is the most recent version in the 9.0 series. You
should *always* use the newest minor version in a series and update
when new versions are released. Otherwise you will hit bugs again that
have been fixed for years.
Regards,
Marti
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Thanks a lot Marti for your response.
Thanks,
Anjali
On Monday, 20 January 2014 3:27 PM, Marti Raudsepp <marti@juffo.org> wrote:
On Mon, Jan 20, 2014 at 11:22 AM, <anjali_524@yahoo.co.in> wrote:
The Postgres version on which the issue was reported is 8.2.2
Do you realize that this version was released almost 7 years ago? The
last bugfix release in the 8.2 series was 8.2.23, only 2 years ago. If
you don't apply bugfixes then you *will* eventually hit bugs.
I verified the issue fix information into postgres release notes
9.0.4, 9.0.15, and 9.1 but could not find anything related to this issue.
It was probably some sort of index corruption, which allowed duplicate
values to be inserted. There have been a dozen bugs of this kind fixed
and it's hard to tell which one.
We have upgraded our Postgres version to 9.0.4
Wait, what? 9.0.15 is the most recent version in the 9.0 series. You
should *always* use the newest minor version in a series and update
when new versions are released. Otherwise you will hit bugs again that
have been fixed for years.
Regards,
Marti
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs