Re: BUG #11025: could not access status of transaction 7 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #11025: could not access status of transaction 7
Date
Msg-id 27346.1406148531@sss.pgh.pa.us
Whole thread Raw
In response to BUG #11025: could not access status of transaction 7  (shiguangsheng@huawei.com)
Responses Re: BUG #11025: could not access status of transaction 7  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
shiguangsheng@huawei.com writes:
> PostgreSQL version: 8.3.17

8.3 is long out of support (and 8.3.17 even more so).

> I added a function that is used to scan the specified table.

You didn't show us enough of that function to be sure, but I rather
suspect that you're failing to pay attention to the
XMIN/XMAX COMMITTED/INVALID status bits.  Once those are set it is
no longer appropriate to try to fetch the actual commit status,
because the system is allowed to truncate away the relevant part of
pg_clog.

            regards, tom lane

pgsql-bugs by date:

Previous
From: shiguangsheng@huawei.com
Date:
Subject: BUG #11025: could not access status of transaction 7
Next
From: Robert Fleming
Date:
Subject: Re: BUG #11028: psql doesn't use 0x01 and 0x02 to inform readline of non-printable PROMPT1 chars