This is strange and as of now I do not have a reliable way of reproducing.
either there is a major blunder on my side that urgently needs being
pointed at and eliminated
or there is something really strange with PG.
I update some rows of a table changing non-primary key column values.
Afterwards some of the updated rows are returned from a query with
the version from before and after the update.
Consequently the PK is detected inconsistent later on and errors are
Longer Version: please see text attachment
server_version | 8.4.7
server_version_num | 80407
OS: NetBSD 5.99.38
account_item 12 GB 6,8079,402 rows
While the update was executing another process was active that was
issuing a sequence of select.
Running that very sequence on a copy clone of the database (before the
worked without such effect.
I had 3 similar occurrences before.
But those were on a DB instance used for development and I could not
verify the primary key was active during update.
Here it is verified it was in place. So the "bad" entries probably could
have been rejected due to PK violation?
Not much input I can give for decent analysis,
but either someone can point me to the obvious
or it is something thats worth being watched for somehow....
pgsql-bugs by date
|Next:||From: Pavel Stehule||Date: 2011-08-17 11:33:58|
|Subject: Re: PG8.4.7: updating rows leaves duplicate rows violating PK|
|Previous:||From: raf||Date: 2011-08-17 05:21:01|
|Subject: BUG #6165: documentation bug in plpgsql-declarations.html and plpgsql-statements.html (or plpgsql parser bug)|