| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the |
| Date: | 2007-08-27 17:59:58 |
| Message-ID: | 5314.1188237598@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Mkz | 2007-08-27 21:45:00 | pgbouncer - pgbouncer: asciidoc manpages from Dimitri Fontaine. |
| Previous Message | Andrew Dunstan | 2007-08-27 17:44:23 | Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-08-27 18:03:46 | Re: MSVC build system |
| Previous Message | Tom Lane | 2007-08-27 17:50:53 | Re: [WIP PATCH] Lazily assign xids for toplevel Transactions |