Re: postgresql 9.6 - cannot freeze committed xmax

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Alexandre Garcia <alexandre(at)vmfarms(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: postgresql 9.6 - cannot freeze committed xmax
Date: 2018-03-01 21:42:50
Message-ID: 20180301214250.h4dcsaizqhrn7y7y@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 2018-03-01 18:32:08 -0300, Alvaro Herrera wrote:
> I pushed my proposed fix all the way back to 9.3.
>
> As I said earlier, I couldn't detect a bug of the sort you describe:
>
> a) as I argued in my previous email, no tuple earlier than the
> relfreezexid should survive, because 9.2 did remove those when
> freezing the table.

You're right, I think I was thinking of the < 9.3.x case where
multixacts weren't removed at all.

Greetings,

Andres Freund

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message girish R G peetle 2018-03-01 22:07:49 pg_dump to fifo file on Linux
Previous Message Alvaro Herrera 2018-03-01 21:32:08 Re: postgresql 9.6 - cannot freeze committed xmax