Re: visibility map corruption

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: visibility map corruption
Дата
Msg-id CAH2-Wzk2T16WtN56MJEkOcW2UN9Hzn7JNMSPERgRL_xZv5Xocg@mail.gmail.com
обсуждение исходный текст
Ответ на RE: visibility map corruption  (Floris Van Nee <florisvannee@Optiver.com>)
Ответы RE: visibility map corruption
Список 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 по дате отправления:

Предыдущее
От: Floris Van Nee
Дата:
Сообщение: RE: visibility map corruption
Следующее
От: Justin Pryzby
Дата:
Сообщение: Re: "debug_invalidate_system_caches_always" is too long