From: | m(dot)mcinness1(at)gmail(dot)com |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #8439: phantom dupe key violation |
Date: | 2013-09-07 17:26:14 |
Message-ID: | E1VIMH0-0007nQ-94@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: 8439
Logged by: Michael McInness
Email address: m(dot)mcinness1(at)gmail(dot)com
PostgreSQL version: 9.2.0
Operating system: Ubuntu 12.0.4
Description:
I apologize in advance -- I cannot reproduce this using a backup database
and after deleting one of the rows in question the issue is resolved, but I
feel compelled to report the problem in case there is a similar issue that
is being tracked:
a query such as 'select * from foo where foo_id = 1' on a table with a
primary key created as such: create table foo (foo_id serial primary
key,...) was producing two rows:
foo_id
--------
1
3
Because it's a production system, I needed to address immediately. After
deleting then re-inserting the row with foo_id = 3, the problem went away,
of course. This really happened -- I wouldn't dream of wasting your time!
Thanks and regards,
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | sabat.jitendra20 | 2013-09-09 07:55:14 | BUG #8440: sevices not started automatically |
Previous Message | Bruce Momjian | 2013-09-07 15:44:47 | Re: BUG #7730: intarray representation of empty arrays |