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 1nA13E-0004kp-Oe for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Jan 2022 02:50:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nA13C-0002Qj-Pf for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Jan 2022 02:50:18 +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 1nA13C-0002Qa-6u for pgsql-hackers@lists.postgresql.org; Wed, 19 Jan 2022 02:50:18 +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 1nA139-0000DC-FK for pgsql-hackers@postgresql.org; Wed, 19 Jan 2022 02:50:16 +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 20J2o7xd440240; Tue, 18 Jan 2022 21:50:07 -0500 From: Tom Lane To: Andres Freund cc: Justin Pryzby , Robert Haas , Andrew Dunstan , pgsql-hackers@postgresql.org, Thomas Munro , Melanie Plageman , Peter Eisentraut , Daniel Gustafsson Subject: Re: Adding CI to our tree In-reply-to: <20220119011626.nw5cvugqfsy3fyob@alap3.anarazel.de> References: <63f3be31-d7c4-0ff4-e5f4-7368863da1bc@dunslane.net> <20220114233411.2byuid4umwjqbhug@alap3.anarazel.de> <20220114235457.GQ14051@telsasoft.com> <87a81b91-87bf-c0bc-7e4f-06dffadcf737@dunslane.net> <20220117181946.bmvubqpzqxlvmgeh@alap3.anarazel.de> <20220117192510.txue5mihjaxlngep@alap3.anarazel.de> <85428.1642447853@sss.pgh.pa.us> <20220117201619.3ltudwhgk2krmoki@alap3.anarazel.de> <20220118210847.GC23027@telsasoft.com> <20220119011626.nw5cvugqfsy3fyob@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Tue, 18 Jan 2022 17:16:26 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <440238.1642560607.1@sss.pgh.pa.us> Date: Tue, 18 Jan 2022 21:50:07 -0500 Message-ID: <440239.1642560607@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I just found one thing making check-world slower than it ought to be: src/test/recovery/t/008_fsm_truncation.pl does $node_primary->append_conf( 'postgresql.conf', qq{ fsync = on wal_log_hints = on max_prepared_transactions = 5 autovacuum = off }); There is no reason for this script to be overriding Cluster.pm's fsync = off setting. This actually causes parallel check-world to fail altogether on florican's host, because the initial fsync of the recovered primary takes more than 3 minutes when there's conflicting I/O traffic, causing pg_ctl to time out. This appears to go back to 917dc7d23 of 2016, so I think it just predates our recognition that we should disable fsync in routine tests. regards, tom lane