Re: BUG #11025: could not access status of transaction 7

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: shiguangsheng(at)huawei(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #11025: could not access status of transaction 7
Date: 2014-07-24 16:54:16
Message-ID: 20140724165415.GH5475@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:
> shiguangsheng(at)huawei(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-07-24 17:22:07 Re: PostgreSQL 9.2.7 on Power 8 / AIX 7.1
Previous Message Rainer Tammer 2014-07-24 15:19:25 PostgreSQL 9.2.7 on Power 8 / AIX 7.1