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

From Andres Freund
Subject Re: postgresql 9.6 - cannot freeze committed xmax
Date
Msg-id 20180228211621.vikbp5s3rwg47455@alap3.anarazel.de
Whole thread Raw
In response to Re: postgresql 9.6 - cannot freeze committed xmax  (Alexandre Garcia <alexandre@vmfarms.com>)
Responses Re: postgresql 9.6 - cannot freeze committed xmax  (Alexandre Garcia <alexandre@vmfarms.com>)
List pgsql-admin
Hi,

On 2018-02-28 21:12:58 +0000, Alexandre Garcia wrote:
> Thanks for your answers, took me a little while to restore a backup from
> before the upgrade on an empty 9.2 server but here we are =>
> https://gist.github.com/kuuji/cc73c3c193a0d58aa0e651fbd7bfec58

Thanks.

> > > > Prod starting throwing the following errors during autovacuum ->
> > 'cannot
> > > > freeze committed xmax <xid>' on 2 different tables. Running vacuum
> > manually
> > > > revealed more tables affected by the same error.

What's an example <xid> in that message that triggers for
problematic_table?  I need that to properly interpret the data you
provided.

Thanks,

Andres


pgsql-admin by date:

Previous
From: Alexandre Garcia
Date:
Subject: Re: postgresql 9.6 - cannot freeze committed xmax
Next
From: Laurenz Albe
Date:
Subject: Re: Reliable WAL file shipping over unreliable network