Re: 8.4.0 data loss / HOT-related bug - Mailing list pgsql-bugs

From Andrew Gierth
Subject Re: 8.4.0 data loss / HOT-related bug
Date
Msg-id 87ws4u7vxx.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: 8.4.0 data loss / HOT-related bug  (Greg Stark <gsstark@mit.edu>)
Responses Re: 8.4.0 data loss / HOT-related bug  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
>>>>> "Greg" == Greg Stark <gsstark@mit.edu> writes:

 Greg> Either of two things are true.
 Greg> Either transaction 6179 committed,
[snip]

This is all missing the point. The row should have been killed by
transaction 4971, NOT 6179. By the time transaction 6179 tried to
do anything with it, it was almost certainly already broken (or
possibly 6179 broke it).

Notice that in the log table, the log entry that records the most
recent update to the row is the one with xmin=4971. There is no
entry in the log table corresponding to 6179.

--
Andrew (irc:RhodiumToad)

pgsql-bugs by date:

Previous
From: Radoslaw Zielinski
Date:
Subject: Re: 8.4.0 data loss / HOT-related bug
Next
From: Hiroshi Inoue
Date:
Subject: Re: BUG #4991: problem with ODBC driver 8.4