Re: 8.4.0 data loss / HOT-related bug

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: gsstark(at)mit(dot)edu (Greg Stark), Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Radoslaw Zielinski <radek(at)pld-linux(dot)org>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: 8.4.0 data loss / HOT-related bug
Date: 2009-08-23 08:53:30
Message-ID: 87ws4u7vxx.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>>>>> "Greg" == Greg Stark <gsstark(at)mit(dot)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)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Hiroshi Inoue 2009-08-23 09:43:43 Re: BUG #4991: problem with ODBC driver 8.4
Previous Message Radoslaw Zielinski 2009-08-23 08:44:43 Re: 8.4.0 data loss / HOT-related bug