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

From Alvaro Herrera
Subject Re: BUG #11025: could not access status of transaction 7
Date
Msg-id 20140724165415.GH5475@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: BUG #11025: could not access status of transaction 7  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #11025: could not access status of transaction 7  (enzesheng <enzesheng@gmail.com>)
List pgsql-bugs
Tom Lane wrote:
> 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.

Also need to check HEAP_XMAX_IS_MULTI.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL 9.2.7 on Power 8 / AIX 7.1
Next
From: David Leverton
Date:
Subject: Re: BUG #10533: 9.4 beta1 assertion failure in autovacuum process