From: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Sending out a request for more buildfarm animals? |
Date: | 2014-05-06 21:01:39 |
Message-ID: | 53694DB3.3080102@fuzzy.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6.5.2014 22:24, Tom Lane wrote:
> 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...)
Now, that's a challenge ;-)
>
> I think testing CLOBBER_FREED_MEMORY would be sensible though.
OK, I've enabled this for now.
Tomas
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2014-05-06 21:04:04 | Re: pg_shmem_allocations view |
Previous Message | Simon Riggs | 2014-05-06 20:47:20 | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers |