Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members
От | Andrew Dunstan |
---|---|
Тема | Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members |
Дата | |
Msg-id | 3f3f3d9d-fccf-318d-5c16-622778b42645@dunslane.net обсуждение исходный текст |
Ответ на | Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members
Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members |
Список | pgsql-hackers |
On 6/22/21 5:11 PM, Tom Lane wrote: > Andrew Dunstan <andrew@dunslane.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. > > Looks OK for the buildfarm patch. I wonder if we just want to run initdb once with --clobber-cache instead of once per locale? cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: