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

From Justin Pryzby
Subject Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
Date
Msg-id 20210815144455.GQ10479@telsasoft.com
Whole thread Raw
In response to Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
On Sun, May 16, 2021 at 04:23:02PM -0400, Tom Lane wrote:
> 1. Fix FullXidRelativeTo to be a little less trusting.  It'd
> probably be sane to make it return FirstNormalTransactionId
> when it'd otherwise produce a wrapped-around FullXid, but is
> there any situation where we'd want it to throw an error instead?
> 
> 2. Change pg_resetwal to not do the above.  It's not entirely
> apparent to me what business it has trying to force
> autovacuum-for-wraparound anyway, but if it does need to do that,
> can we devise a less klugy method?
> 
> It also seems like some assertions in procarray.c would be a
> good idea.  With the attached patch, we get through core
> regression just fine, but the pg_upgrade test fails immediately
> after the "Resetting WAL archives" step.

#2 is done as of 74cf7d46a.

Is there a plan to include Tom's procarray assertions ?

-- 
Justin



pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series)
Next
From: Hans Buschmann
Date:
Subject: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode