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 1nemlr-0006kP-4K for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Apr 2022 23:51:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nemlp-0004S5-Qz for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Apr 2022 23:51:33 +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 1nemlp-0004Rw-I8 for pgsql-hackers@lists.postgresql.org; Wed, 13 Apr 2022 23:51:33 +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 1nemlj-00050p-7q for pgsql-hackers@lists.postgresql.org; Wed, 13 Apr 2022 23:51:32 +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 23DNpNDL1365925; Wed, 13 Apr 2022 19:51:23 -0400 From: Tom Lane To: Peter Geoghegan cc: Andres Freund , David Rowley , PostgreSQL Hackers Subject: Re: Intermittent buildfarm failures on wrasse In-reply-to: References: <1346227.1649887693@sss.pgh.pa.us> <1349964.1649890446@sss.pgh.pa.us> <9F59C4BB-3C82-44B0-9B10-4A2CCC3DE552@anarazel.de> <1364997.1649893086@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Wed, 13 Apr 2022 16:45:44 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1365923.1649893883.1@sss.pgh.pa.us> Date: Wed, 13 Apr 2022 19:51:23 -0400 Message-ID: <1365924.1649893883@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Geoghegan writes: > On Wed, Apr 13, 2022 at 4:38 PM Tom Lane wrote: >> It seems like a reliable fix might require test_setup to wait >> for any background autovac to exit before it does its own >> vacuums. Ick. > This is hardly a new problem, really. I wonder if it's worth inventing > a comprehensive solution. Yeah, we have band-aided around this type of problem repeatedly. Making a fix that's readily accessible from any test script seems like a good idea. regards, tom lane