Date: Thu, 24 Mar 2022 19:14:02 -0700
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>,
	Daniel Gustafsson <daniel@yesql.se>,
	Kyotaro Horiguchi <horikyota.ntt@gmail.com>, deniel1495@mail.ru,
	Ibrar Ahmed <ibrar.ahmad@gmail.com>, tejeswarm@hotmail.com,
	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
Message-ID: <20220325021402.r22saxtwuqu3bbil@alap3.anarazel.de>
References: <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>
 <3167047.1648169107@sss.pgh.pa.us>
 <CA+Tgmoa_TAJsUnFWzTevg=FzgXFyiHLJAY_L-jMDA=mH=ytysg@mail.gmail.com>
 <3170060.1648171358@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3170060.1648171358@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/20220325021402.r22saxtwuqu3bbil%40alap3.anarazel.de>
Precedence: bulk

Hi,

On 2022-03-24 21:22:38 -0400, Tom Lane wrote:
> serinus is 0-for-3 since then, and dragonet 0-for-4, so we can be pretty
> confident that the failure is repeatable for them.

That's weird. They run on the same host, but otherwise they have very little
in common. There's plenty other animals running on the same machine that
didn't report errors.

I copied serinus' configuration, ran the tests repeatedly, without reproducing
the failure so far. Odd.

Combined with the replslot failure I'd be prepared to think the machine has
issues, except that the replslot thing triggered on other machines too.


I looked through logs on the machine without finding anything indicating
something odd.

I turned on keep_error_builds for serinus. Hopefully that'll leave us with
on-disk files to inspect.

Greetings,

Andres Freund