Re: postgresql 9.6 - cannot freeze committed xmax

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alexandre Garcia <alexandre(at)vmfarms(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "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 21:24:01
Message-ID: 20180228212401.6yoqyv2a45zv7ph6@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi Alexandre, Alvaro,

Please not that we try not to top-post on this list.

Alvaro,

On 2018-02-28 21:17:08 +0000, Alexandre Garcia wrote:
> Oh yes sorry => `ERROR: cannot freeze committed xmax 43076385` on that
> same table

In light of
Latest checkpoint's NextXID: 0/128653693
I find this confusing.

Alexandre, did you ever use pg_resetxlog on that cluster?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alexandre Garcia 2018-02-28 21:44:03 Re: postgresql 9.6 - cannot freeze committed xmax
Previous Message MichaelDBA 2018-02-28 21:21:29 Re: Postgresql | Vacuum information