Re: visibility map corruption

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Floris Van Nee <florisvannee(at)optiver(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: visibility map corruption
Date: 2021-07-06 17:58:08
Message-ID: 20210706175808.GC26994@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 6, 2021 at 10:32:24AM -0700, Peter Geoghegan wrote:
> On Tue, Jul 6, 2021 at 10:27 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > OK, this is confirmation that the pg_resetwal bug, and its use by
> > pg_upgrade, is a serious issue that needs to be addressed. I am
> > prepared to work on it now.
>
> To be clear, I'm not 100% sure that this is related to the pg_upgrade
> + "pg_resetwal sets oldestXid to an invented value" issue. I am sure
> that that is a serious issue that needs to be addressed sooner rather
> than later, though.

Well, pg_upgrade corruptions are rare, but so is modifying
autovacuum_freeze_max_age. If we have a corruption and we know
autovacuum_freeze_max_age was modified, odds are that is the cause.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

If only the physical world exists, free will is an illusion.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2021-07-06 18:20:49 Re: [PATCH] Pull general SASL framework out of SCRAM
Previous Message Tom Lane 2021-07-06 17:52:10 Re: Planning time grows exponentially with levels of nested views