Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members

Tom Lane <tgl@sss.pgh.pa.us>

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>
Date: 2021-07-01T17:17:42Z
Lists: 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



Commits

  1. Add --clobber-cache option to initdb, for CCA testing.