Skip site navigation (1) Skip section navigation (2)

Re: 8.4.0 data loss / HOT-related bug

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Radoslaw Zielinski <radek(at)pld-linux(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 8.4.0 data loss / HOT-related bug
Date: 2009-08-21 16:12:50
Message-ID: 407d949e0908210912yc8679d9j8d369015ab67f0e5@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, Aug 21, 2009 at 5:03 PM, Greg Stark<gsstark(at)mit(dot)edu> wrote:
> On Fri, Aug 21, 2009 at 4:04 PM, Radoslaw Zielinski<radek(at)pld-linux(dot)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: promocje.page
Description: application/octet-stream (2.6 KB)

In response to

Responses

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2009-08-21 16:15:26
Subject: Re: 8.4.0 data loss / HOT-related bug
Previous:From: Greg StarkDate: 2009-08-21 16:03:00
Subject: Re: 8.4.0 data loss / HOT-related bug

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group