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

Re: 8.4.0 data loss / HOT-related bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: 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-21 16:33:03
Message-ID: 5696.1250872383@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> I wonder if this could be explained by xid=6179 not marked as committed
> in clog.  I'd try flipping that bit and see what happens ...

Once the row's been marked XMAX_INVALID, changing clog won't change that
marking ...

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Greg StarkDate: 2009-08-21 16:38:17
Subject: Re: 8.4.0 data loss / HOT-related bug
Previous:From: Sebastien LardiereDate: 2009-08-21 16:26:11
Subject: BUG #5004: pg_freespacemap make a SegFault

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