Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the
Date
Msg-id 46D30D77.2060805@dunslane.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>   
>> [redirected to -hackers]
>>     
>
>   
>> Tom Lane wrote:
>>     
>>> Found by trying to run the regression tests with CLOBBER_CACHE_ALWAYS enabled.
>>> Maybe we should try to do that on a regular basis --- it's awfully slow,
>>> but perhaps some fast buildfarm machine could do it once in awhile.
>>>       
>
>   
>> We currently don't have any way of providing for settings other than via 
>> the configure script options. We could in theory make provision for 
>> adding stuff to pg_config_manual.h, although it would be a bit more 
>> difficult in the vpath (I guess for vpath we could just blow that file 
>> away along with the files bison, flex etc. lob in the repo).
>>     
>
> This particular issue could be implemented just by adding
> -DCLOBBER_CACHE_ALWAYS to CFLAGS (or CPPFLAGS if you want to be anal
> about it).  I suppose that no new buildfarm mechanism is required ---
> someone just needs to set up an animal configured that way, and
> scheduled to run only maybe once a week or something like that.
>
>             
>   

Ah. Ok. That makes sense. How long does such a regression run usually take?

cheers

andrew


pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: [WIP PATCH] Lazily assign xids for toplevel Transactions
Next
From: Tom Lane
Date:
Subject: Re: [WIP PATCH] Lazily assign xids for toplevel Transactions