From: | pgsql-bugs(at)postgresql(dot)org |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Duplicate records leaking into unique indexed tables |
Date: | 2000-12-14 06:29:01 |
Message-ID: | 200012140629.eBE6T1785639@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Doug Mitchell (pgsql(at)dougmitchell(dot)com) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Duplicate records leaking into unique indexed tables
Long Description
PostgreSQL 7.0.3 on RedHat 7.0
I have some fairly large (2-3 million rows) tables with a PRIMARY KEY that created a valid unique index. After a few days of high-concurrency updates, vacuum says the it "can not insert a duplicate record into tablename_pkey". I'm fairly sure that my application would crash if an INSERT failed due to key duplications, so I have to believe that this is internal to PG. Maybe the index is pointing to both the current and a previous version of the same tuple.
I didn't see this until I upgraded from 7.0 to 7.0.3, but I was not looking for it.
Thanks,
Doug
Sample Code
No file was uploaded with this report
From | Date | Subject | |
---|---|---|---|
Next Message | Gena Gurchonok | 2000-12-14 07:15:45 | Windows ODBC tables list (with 7.1 CVS) |
Previous Message | Bruno Wolff III | 2000-12-14 06:04:46 | More on previous bug report |