BUG #8891: Duplicate Primary Key

From: anjali_524(at)yahoo(dot)co(dot)in
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #8891: Duplicate Primary Key
Date: 2014-01-20 09:22:09
Message-ID: 20140120092209.26704.92017@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 8891
Logged by: Anjali Arora
Email address: anjali_524(at)yahoo(dot)co(dot)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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Marti Raudsepp 2014-01-20 09:55:42 Re: BUG #8891: Duplicate Primary Key
Previous Message Jeevan Chalke 2014-01-20 06:23:58 Re: [BUGS] surprising to_timestamp behavior