ERROR: simple_heap_delete: tuple already updated by self

Started by utsavover 16 years ago2 messagesgeneral
Jump to latest
#1utsav
utsav.turray@newgen.co.in

Dear All ,

I am using postgres 7.3. on RHEL 4.0

I have table on which there are duplicate rows even though there is a primary key constraint.I dont know how the rows got duplicate , because in my s/w there is no such possibility.

Wel till now i used to delete the row duplicate row with the help of OIDS. But on a prticular server while deleting the duplicate row i got error "ERROR: simple_heap_delete: tuple already updated by self "

If I dump the table using pg_dump and restore it in a temorary table without primary key constarint, then i am able to delete the duplicate row.

Kindly help in identifying and solving this problem , and why the rows are getting duplicate automatically

Regards,
Utsav
Disclaimer :- This e-mail and any attachment may contain confidential, proprietary or legally privileged information. If you are not the original intended recipient and have erroneously received this message, you are prohibited from using, copying, altering or disclosing the content of this message. Please delete it immediately and notify the sender. Newgen Software Technologies Ltd (NSTL) accepts no responsibilities for loss or damage arising from the use of the information transmitted by this email including damages from virus and further acknowledges that no binding nature of the message shall be implied or assumed unless the sender does so expressly with due authority of NSTL.

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: utsav (#1)
Re: ERROR: simple_heap_delete: tuple already updated by self

"utsav" <utsav.turray@newgen.co.in> writes:

I am using postgres 7.3. on RHEL 4.0

7.3.what? If it's not 7.3.21 then an update would probably be worth
your time. In particular there were fixes in 7.3.14 and 7.3.20 that
could possibly explain this.

If it is 7.3.21, then I think an upgrade to a newer major release series
is your only hope of getting a fix. The PG community declared 7.3.x to
be EOL nearly two years ago, and I believe that Red Hat's policy is
they'll only consider fixing security bugs in it at this point. Which
this is not.

If you can demonstrate the same type of failure in a currently supported
release, we'd take more of an interest, but fixing 7.3 isn't going to
happen :-(

regards, tom lane