From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Andres Freund <andres@anarazel.de>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Subject: Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
Date: Sun, 16 May 2021 18:21:21 -0400
Message-ID: <2595981.1621203681@sss.pgh.pa.us> (raw)
In-Reply-To: <CAH2-Wz=Pdfhd0Pc3g6odxkgBP9P6nsp1uaiR0JYRac9fYyYGrQ@mail.gmail.com>
References: <f03ea04a-9b77-e371-9ab9-182cb35db1f9@iki.fi>
<2472976.1621117273@sss.pgh.pa.us>
<2591376.1621196582@sss.pgh.pa.us>
<CAH2-Wz=Pdfhd0Pc3g6odxkgBP9P6nsp1uaiR0JYRac9fYyYGrQ@mail.gmail.com>
Peter Geoghegan <pg@bowt.ie> writes:
> On Sun, May 16, 2021 at 1:23 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> And the reason oldestXID contains that is that pg_upgrade applied
>> pg_resetwal, which does this:
>> * For the moment, just set oldestXid to a value that will force
>> * immediate autovacuum-for-wraparound.
> This same pg_resetwal code has probably caused quite a few problems on
> pg_upgrade'd databases:
> https://postgr.es/m/20210423234256.hwopuftipdmp3okf@alap3.anarazel.de
Hm, yeah. I'm not sure if transferring the value forward from the
old cluster is entirely safe, but if it is, that seems like a
promising route to a fix. (We should still have more sanity checking
around the GlobalVis code, though.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pg@bowt.ie, hlinnaka@iki.fi, andres@anarazel.de, pryzby@telsasoft.com
Subject: Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
In-Reply-To: <2595981.1621203681@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox