Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1liPTb-0003oF-Ex for pgsql-hackers@arkaria.postgresql.org; Sun, 16 May 2021 22:43:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1liPTa-0001kd-6k for pgsql-hackers@arkaria.postgresql.org; Sun, 16 May 2021 22:43:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1liPTZ-0001kU-VP for pgsql-hackers@lists.postgresql.org; Sun, 16 May 2021 22:43:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1liPTX-0003g3-P0 for pgsql-hackers@postgresql.org; Sun, 16 May 2021 22:43:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 14GMgrJl2601446; Sun, 16 May 2021 18:42:53 -0400 From: Tom Lane To: Andres Freund cc: Peter Geoghegan , Heikki Linnakangas , pgsql-hackers , Justin Pryzby Subject: Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619 In-reply-to: <20210516223513.outnhdfibafroqc4@alap3.anarazel.de> References: <2472976.1621117273@sss.pgh.pa.us> <2591376.1621196582@sss.pgh.pa.us> <2595981.1621203681@sss.pgh.pa.us> <20210516223513.outnhdfibafroqc4@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Sun, 16 May 2021 15:35:13 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2601444.1621204973.1@sss.pgh.pa.us> Date: Sun, 16 May 2021 18:42:53 -0400 Message-ID: <2601445.1621204973@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andres Freund writes: > On 2021-05-16 18:21:21 -0400, Tom Lane wrote: >> 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.) > Why would it not be safe? I'm just wondering about the catalog tuples set up by pg_upgrade itself. If they're all frozen then they probably don't matter to this, but it might take some thought. > I think we should remove the heuristic thing from pg_resetwal entirely, > and error out if next-xid is set to something too far away from oldest > xid, unless oldexid is also specified. Seems plausible ... regards, tom lane