Re: visibility map corruption - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: visibility map corruption
Date
Msg-id CAH2-Wzk2T16WtN56MJEkOcW2UN9Hzn7JNMSPERgRL_xZv5Xocg@mail.gmail.com
Whole thread Raw
In response to RE: visibility map corruption  (Floris Van Nee <florisvannee@Optiver.com>)
Responses RE: visibility map corruption  (Floris Van Nee <florisvannee@Optiver.com>)
List pgsql-hackers
On Sun, Jul 4, 2021 at 2:26 PM Floris Van Nee <florisvannee@optiver.com> wrote:
> > Have you ever used pg_upgrade on this database?
> >
>
> Yes. The last time (from v11 to v12) was in October 2020. The transaction id in the tuples (the one PG is trying to
checkin the tx log) dated from February 2021. I do believe (but am not 100% certain) that the affected table already
existedat the time of the last pg_upgrade though. 

I wonder if it's related to this issue:

https://www.postgresql.org/message-id/20210423234256.hwopuftipdmp3okf@alap3.anarazel.de

Have you increased autovacuum_freeze_max_age from its default? This
already sounds like the kind of database where that would make sense.

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Floris Van Nee
Date:
Subject: RE: visibility map corruption
Next
From: Justin Pryzby
Date:
Subject: Re: "debug_invalidate_system_caches_always" is too long