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 1m03WV-0006Kg-J6 for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Jul 2021 14:55:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m03WS-0004TU-4P for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Jul 2021 14:55:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m03WR-0004TK-T3 for pgsql-hackers@lists.postgresql.org; Sun, 04 Jul 2021 14:55:03 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m03WK-0001bD-R7 for pgsql-hackers@lists.postgresql.org; Sun, 04 Jul 2021 14:55:02 +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 164Esoc21334265; Sun, 4 Jul 2021 10:54:50 -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> <702694.1625159862@sss.pgh.pa.us> <1289102.1625353189@sss.pgh.pa.us> Comments: In-reply-to Andrew Dunstan message dated "Sun, 04 Jul 2021 06:49:13 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1334263.1625410490.1@sss.pgh.pa.us> Date: Sun, 04 Jul 2021 10:54:50 -0400 Message-ID: <1334264.1625410490@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/3/21 6:59 PM, Tom Lane wrote: >> So I think it's ready to go into the buildfarm, modulo any >> cosmetic work you might want to do. > Yeah, I'm looking at it now. A couple of things: I think we should > probably call the setting 'use_clobber_cache_always' since that's what > it does. And I think we should probably put in a sanity check to make it > incompatible with any -DCLOBBER_CACHE_* define in CPPFLAGS. > Thoughts? No objections here. regards, tom lane