Re: postgresql 9.6 - cannot freeze committed xmax - Mailing list pgsql-admin

From Alexandre Garcia
Subject Re: postgresql 9.6 - cannot freeze committed xmax
Date
Msg-id CAPYLKR4BqAa-FBM6QoEj8OYZXafu9RUEusoecrpo0ZoBxoY4Wg@mail.gmail.com
Whole thread Raw
In response to Re: postgresql 9.6 - cannot freeze committed xmax  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: postgresql 9.6 - cannot freeze committed xmax  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List 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 by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: postgresql 9.6 - cannot freeze committed xmax
Next
From: Alvaro Herrera
Date:
Subject: Re: postgresql 9.6 - cannot freeze committed xmax