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 1lz0Jx-0007dI-Tx for pgsql-hackers@arkaria.postgresql.org; Thu, 01 Jul 2021 17:17:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lz0Jw-0000fA-LH for pgsql-hackers@arkaria.postgresql.org; Thu, 01 Jul 2021 17:17:48 +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 1lz0Jw-0000f2-DM for pgsql-hackers@lists.postgresql.org; Thu, 01 Jul 2021 17:17:48 +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 1lz0Ju-0005Ms-2w for pgsql-hackers@lists.postgresql.org; Thu, 01 Jul 2021 17:17:47 +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 161HHg0c702695; Thu, 1 Jul 2021 13:17:42 -0400 From: Tom Lane To: Andrew Dunstan cc: pgsql-hackers@lists.postgresql.org, Peter Eisentraut Subject: Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members In-reply-to: References: <1582507.1624227029@sss.pgh.pa.us> <467e9f1a-f440-4875-2677-36f52f556f62@dunslane.net> <1799344.1624396289@sss.pgh.pa.us> <3f3f3d9d-fccf-318d-5c16-622778b42645@dunslane.net> <693603.1625151671@sss.pgh.pa.us> Comments: In-reply-to Andrew Dunstan message dated "Thu, 01 Jul 2021 13:03:00 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <702693.1625159862.1@sss.pgh.pa.us> Date: Thu, 01 Jul 2021 13:17:42 -0400 Message-ID: <702694.1625159862@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > On 7/1/21 11:01 AM, Tom Lane wrote: >> I'm inclined to argue that it's okay to sneak the initdb change into >> v14, on the grounds that it's needed to fully exploit the change >> from CLOBBER_CACHE_ALWAYS to debug_invalidate_system_caches_always. >> Without it, there is no way to do CCA testing on the bootstrap process >> except by reverting to the old hard-wired way of doing things. >> >> Having pushed that, we could try out the buildfarm side of the >> change and verify it's okay. > Seems reasonable. I don't have a CCA animal any more, but I guess I > could set up a test. I can run a test here --- I'll commandeer sifaka for awhile, since that's the fastest animal I have. regards, tom lane