| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: strange buildfarm failure on lionfish |
| Date: | 2007-07-24 20:06:08 |
| Message-ID: | 15450.1185307568@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> While I don't have any very strong objection to putting an ORDER BY
>> on these particular queries, I'm worried about how many other regression
>> tests will now start showing random failures. We have an awful lot
>> of small tables in the tests ...
> Maybe what we could do is set higher thresholds for the regression
> database with ALTER DATABASE.
That seems to make sense at least as a short-term response. We weren't
seeing buildfarm failures with the previous defaults, so setting those
values with ALTER oughta do it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-07-24 20:21:27 | Re: pgcrypto & strong ciphers limitation |
| Previous Message | Marko Kreen | 2007-07-24 20:04:17 | Re: pgcrypto & strong ciphers limitation |