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

From Greg Stark
Subject Re: 8.4.0 data loss / HOT-related bug
Date
Msg-id 407d949e0908210912yc8679d9j8d369015ab67f0e5@mail.gmail.com
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  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: 8.4.0 data loss / HOT-related bug  (Radoslaw Zielinski <radek@pld-linux.org>)
List pgsql-bugs
On Fri, Aug 21, 2009 at 5:03 PM, Greg Stark<gsstark@mit.edu> wrote:
> On Fri, Aug 21, 2009 at 4:04 PM, Radoslaw Zielinski<radek@pld-linux.org> wrote:
>
> Here's a dump of that page btw.
... [crap word-wrapped by gmail]

Sorry, clearly gmail sucks for posting things that you actually care
about how they're formatted. I've attached the page dump.

It looks like the row *was* updated by transaction 6179 and the new
version was stored in line pointer 12. However  it's marked
XMAX_INVALID which means at least somebody at some point thought 6179
had aborted and marked that hint bit.

Do we have any tools to look up a transaction id  status in the clog?
Or alternatively do you have all the wal logs and could you run
xlogdump on them looking for transaction id 6179?

--
greg
http://mit.edu/~gsstark/resume.pdf

Attachment

pgsql-bugs by date:

Previous
From: Greg Stark
Date:
Subject: Re: 8.4.0 data loss / HOT-related bug
Next
From: Alvaro Herrera
Date:
Subject: Re: 8.4.0 data loss / HOT-related bug