Re: postgresql 9.6 - cannot freeze committed xmax

Поиск
Список
Период
Сортировка
От Alexandre Garcia
Тема Re: postgresql 9.6 - cannot freeze committed xmax
Дата
Msg-id CAPYLKR4BqAa-FBM6QoEj8OYZXafu9RUEusoecrpo0ZoBxoY4Wg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: postgresql 9.6 - cannot freeze committed xmax  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: postgresql 9.6 - cannot freeze committed xmax
Список pgsql-admin


Ooh.

If you SELECT FOR UPDATE a tuple in 9.2, bit 0x0040 gets set in
infomask, and nothing else.  If you pg_upgrade and later try to freeze
such a tuple, it will fail with the error reported.

The correct test to use is HEAP_XMAX_IS_LOCKED_ONLY, which also tests
for the above condition.

I will verify this theory and push a patch shortly, if it proves
correct.


Oh good news  :). I have my old 9.2 around if you need me to do more testing on it.

В списке pgsql-admin по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: postgresql 9.6 - cannot freeze committed xmax
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: postgresql 9.6 - cannot freeze committed xmax