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

From Alvaro Herrera
Subject Re: 8.4.0 data loss / HOT-related bug
Date
Msg-id 20090821161726.GF5487@alvh.no-ip.org
Whole thread Raw
In response to Re: 8.4.0 data loss / HOT-related bug  (Greg Stark <gsstark@mit.edu>)
List pgsql-bugs
Greg Stark wrote:

> 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.

Hmm, but LP 12 shouldn't have len=0 then, no?  Unless it has been
clobbered by vacuum or HOT pruning, I guess ...

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: 8.4.0 data loss / HOT-related bug
Next
From: ""
Date:
Subject: BUG #5001: can not prepare for where $1 is null