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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #11025: could not access status of transaction 7
Дата
Msg-id 27346.1406148531@sss.pgh.pa.us
обсуждение исходный текст
Ответ на BUG #11025: could not access status of transaction 7  (shiguangsheng@huawei.com)
Ответы Re: BUG #11025: could not access status of transaction 7  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список 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 по дате отправления:

Предыдущее
От: shiguangsheng@huawei.com
Дата:
Сообщение: BUG #11025: could not access status of transaction 7
Следующее
От: Robert Fleming
Дата:
Сообщение: Re: BUG #11028: psql doesn't use 0x01 and 0x02 to inform readline of non-printable PROMPT1 chars