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 1n9utV-0003KE-6H for pgsql-committers@arkaria.postgresql.org; Tue, 18 Jan 2022 20:15:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n9utT-0004ER-Eq for pgsql-committers@arkaria.postgresql.org; Tue, 18 Jan 2022 20:15:51 +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 1n9utT-0004EH-7g for pgsql-committers@lists.postgresql.org; Tue, 18 Jan 2022 20:15:51 +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 1n9utQ-0005aG-He for pgsql-committers@lists.postgresql.org; Tue, 18 Jan 2022 20:15:49 +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 20IKFiuw374644; Tue, 18 Jan 2022 15:15:44 -0500 From: Tom Lane To: Thomas Munro cc: Andres Freund , Michael Paquier , Thomas Munro , pgsql-committers Subject: Re: pgsql: Test replay of regression tests, attempt II. In-reply-to: References: <20220117203746.oj43254j5jurbneu@alap3.anarazel.de> Comments: In-reply-to Thomas Munro message dated "Wed, 19 Jan 2022 07:56:38 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <374642.1642536944.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 18 Jan 2022 15:15:44 -0500 Message-ID: <374643.1642536944@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > Alright, I've pushed a change like that. Let's see if that clears it > up. Nope: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Drorqual&dt=3D202= 2-01-18%2019%3A50%3A57 That reloptions test has been there awhile, and we weren't seeing issues with it before. What about the replication environment would cause VACUUM to behave differently? Maybe it thinks there are non-removable tuples because the walsender is holding back global xmin? regards, tom lane