Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
Date
Msg-id 2595981.1621203681@sss.pgh.pa.us
Whole thread Raw
In response to Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
Next
From: Andres Freund
Date:
Subject: Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619