Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members
Date: 2021-06-22 21:11:29
Message-ID: 1799344.1624396289@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 6/20/21 6:10 PM, Tom Lane wrote:
>> (3) Since this only works in v14 and up, older branches would
>> have to fall back to -DCLOBBER_CACHE_ALWAYS. Perhaps we could
>> improve the buildfarm client script so that buildfarm owners
>> just configure "clobber_cache_testing => 1" and then the script
>> would do the right branch-dependent thing.

> Maybe. Let's see what you come up with.

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.

regards, tom lane

Attachment Content-Type Size
initdb-cache-clobber-option-1.patch text/x-diff 4.1 KB
buildfarm-clobber-option-1.patch text/x-diff 2.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mike 2021-06-22 22:07:53 Fwd: Emit namespace in post-copy output
Previous Message Alexander Korotkov 2021-06-22 20:42:47 Re: Decouple operator classes from index access methods