From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Sending out a request for more buildfarm animals? |
Date: | 2014-05-06 20:24:20 |
Message-ID: | 16901.1399407860@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tomas Vondra <tv(at)fuzzy(dot)cz> writes:
> I recall there was a call for more animals with CLOBBER_CACHE_ALWAYS
> some time ago, so I went and enabled that on all three animals. Let's
> see how long that will take.
> I see there are more 'clobber' options in the code: CLOBBER_FREED_MEMORY
> and CLOBBER_CACHE_RECURSIVELY. Would that be a good idea to enable these
> as well?
> The time requirements will be much higher (especially for the
> RECURSIVELY option), but running that once a week shouldn't be a big
> deal - the machine is pretty much dedicated to the buildfarm.
I've never had the patience to run the regression tests to completion with
CLOBBER_CACHE_RECURSIVELY at all, let alone do it on a regular basis.
(I wonder if there's some easy way to run it for just a few regression
tests...)
I think testing CLOBBER_FREED_MEMORY would be sensible though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2014-05-06 20:30:26 | Re: Wanted: jsonb on-disk representation documentation |
Previous Message | Tom Lane | 2014-05-06 20:18:50 | Re: Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) |