Re: Error on vacuum: xmin before relfrozenxid

From: Andres Freund <andres(at)anarazel(dot)de>
To: Paolo Crosato <paolo(dot)crosato(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Error on vacuum: xmin before relfrozenxid
Date: 2018-05-23 18:32:38
Message-ID: 20180523183238.nfrzh35c7n4mhfuq@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 2018-05-22 16:39:58 -0700, Andres Freund wrote:
> Hi,
>
> On 2018-05-23 00:04:26 +0200, Paolo Crosato wrote:
> > I managed to recover the log of the first time we run into the issue, the
> > error was the same but on template1:
> >
> > May 8 11:26:46 xxx postgres[32543]: [1154-1] user=,db=,client= ERROR:
> > found xmin 2600758304 from before relfrozenxid 400011439
> > May 8 11:26:46 xxx postgres[32543]: [1154-2] user=,db=,client= CONTEXT:
> > automatic vacuum of table "template1.pg_catalog.pg_authid"
>
> pg_authid (along with a few other tables) is shared between
> databases. So that's just hte same error. At which rate are you
> creating / updating database users / roles?

Other questions:
- did you ever use VACUUM FULL or CLUSTER on pg_authid (or just on all
tables)?
- Did you have any failovers?
- Do you use logical replication?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2018-05-23 19:35:57 Re: Insert data if it is not existing
Previous Message David G. Johnston 2018-05-23 17:00:49 Re: Insert data if it is not existing

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-05-23 19:18:28 Re: printf format selection vs. reality
Previous Message Andrew Dunstan 2018-05-23 18:00:18 Re: [PATCH] Clear up perlcritic 'missing return' warning