Re: postgresql 9.6 - cannot freeze committed xmax

From: Alexandre Garcia <alexandre(at)vmfarms(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Andres Freund <andres(at)anarazel(dot)de>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: postgresql 9.6 - cannot freeze committed xmax
Date: 2018-02-28 23:05:02
Message-ID: CAPYLKR4BqAa-FBM6QoEj8OYZXafu9RUEusoecrpo0ZoBxoY4Wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alvaro Herrera 2018-02-28 23:30:19 Re: postgresql 9.6 - cannot freeze committed xmax
Previous Message Alvaro Herrera 2018-02-28 22:56:43 Re: postgresql 9.6 - cannot freeze committed xmax