From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
cc: pgsql-hackers@lists.postgresql.org,
        Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Subject: Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm
 members
In-reply-to: <3f3f3d9d-fccf-318d-5c16-622778b42645@dunslane.net>
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>
Comments: In-reply-to Andrew Dunstan <andrew@dunslane.net>
	message dated "Wed, 23 Jun 2021 09:21:02 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <693602.1625151671.1@sss.pgh.pa.us>
Date: Thu, 01 Jul 2021 11:01:11 -0400
Message-ID: <693603.1625151671@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/693603.1625151671%40sss.pgh.pa.us>
Precedence: bulk

Andrew Dunstan <andrew@dunslane.net> writes:
> On 6/22/21 5:11 PM, Tom Lane wrote:
>> Here's a couple of draft-quality patches --- one for initdb, one
>> for the buildfarm --- to implement this idea.  These are just
>> lightly tested; in particular I've not had the patience to run
>> full BF cycles to see how much is actually saved.

> Looks OK for the buildfarm patch. I wonder if we just want to run initdb
> once with --clobber-cache instead of once per locale?

So, where do we want to go with these?

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.

			regards, tom lane