Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members
Date
Msg-id 702694.1625159862@sss.pgh.pa.us
Whole thread Raw
In response to Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> 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



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members
Next
From: Jacob Champion
Date:
Subject: Re: Remove unused code from the KnownAssignedTransactionIdes submodule