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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1nXY4y-0000su-Co
	for pgsql-hackers@arkaria.postgresql.org; Fri, 25 Mar 2022 00:45:24 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1nXY4x-0006fn-AZ
	for pgsql-hackers@arkaria.postgresql.org; Fri, 25 Mar 2022 00:45:23 +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 <tgl@sss.pgh.pa.us>)
	id 1nXY4w-0006fd-W3
	for pgsql-hackers@lists.postgresql.org; Fri, 25 Mar 2022 00:45:22 +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 <tgl@sss.pgh.pa.us>)
	id 1nXY4u-0002mf-KW
	for pgsql-hackers@postgresql.org; Fri, 25 Mar 2022 00:45:21 +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 22P0j7Wf3167048;
	Thu, 24 Mar 2022 20:45:07 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, deniel1495@mail.ru,
        Ibrar Ahmed <ibrar.ahmad@gmail.com>, tejeswarm@hotmail.com,
        Andres Freund <andres@anarazel.de>, hlinnaka <hlinnaka@iki.fi>,
        Masahiko Sawada <masahiko.sawada@2ndquadrant.com>,
        "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
        Daniel Wood <hexexpert@comcast.net>
Subject: Re: Corruption during WAL replay
In-reply-to: 
 <CA+TgmoYhFvsNedWw9eRJXPevy-RytpRMofbyETtU1SxUCG16-Q@mail.gmail.com>
References: 
 <CA+TgmoYhYrMajsDFMN4r0c4d93MdxxsJdgDVe01FSHm0M3NFyg@mail.gmail.com>
 <20220316.141432.2298656526174566963.horikyota.ntt@gmail.com>
 <CA+TgmobNVosCR02Wpfa2QFnGwu66b81BcX+r2T_6u719E9wBwQ@mail.gmail.com>
 <20220318.102109.162855329039722212.horikyota.ntt@gmail.com>
 <CA+TgmoYqgB8NjTgw6pZsA-RVo4qF8i9CPfqK07sjs6DLGCDf6Q@mail.gmail.com>
 <3152696.1648159485@sss.pgh.pa.us>
 <CA+TgmoYG4-P8PUWPVZyCjR0_kUwfY0KFRJcO7WGO2fi7icGTpA@mail.gmail.com>
 <CA+TgmoYhFvsNedWw9eRJXPevy-RytpRMofbyETtU1SxUCG16-Q@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Thu, 24 Mar 2022 20:39:27 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3167046.1648169107.1@sss.pgh.pa.us>
Date: Thu, 24 Mar 2022 20:45:07 -0400
Message-ID: <3167047.1648169107@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/3167047.1648169107%40sss.pgh.pa.us>
Precedence: bulk

Robert Haas <robertmhaas@gmail.com> writes:
> And ... right after hitting send, I see that the recovery check
> failures are under separate troubleshooting and thus probably
> unrelated.

Yeah, we've been chasing those for months.

> But that leaves me even more confused. How can a change to
> only the server code cause a client utility to fail to detect
> corruption that is being created by Perl while the server is stopped?

Hmm, I'd supposed that the failing test cases were new as of 412ad7a55.
Now I see they're not, which indeed puts quite a different spin on
things.  Your thought about maybe the server isn't shut down yet is
interesting --- did 412ad7a55 touch anything about the shutdown
sequence?

			regards, tom lane