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

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the
Date
Msg-id 5314.1188237598@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> 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?

On my x86_64 machine (dual 2.8GHz Xeon EM64T) it's on the order of two
or three hours --- I haven't timed it carefully, but somewhere along
there.  That's just for the core regression tests, I've never tried
contrib or PL tests.

It should be a separate animal, and not something that an existing one
does every-so-often, or we might mistake anything it finds for an
irreproducible transient failure.  Consistent failures on the same
animal will stand out of the noise, though.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [WIP PATCH] Lazily assign xids for toplevel Transactions
Next
From: Andrew Dunstan
Date:
Subject: Re: MSVC build system