| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Windows buildfarm failures |
| Date: | 2007-01-19 18:47:50 |
| Message-ID: | 45B11256.3070008@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
>
> Perhaps we could extend pg_regress to allow "--max-connections=auto"
> which would instruct it to set its connection limit to the server's
> actual max_connections minus superuser reserved slots (and probably
> minus a couple more to allow for backend shutdown time etc). Then the
> buildfarm could use that, while we'd leave the behavior alone for normal
> manual regression tests.
>
>
This seems needlessly complex. We can tolerate occasional intermittent
failures on buildfarm, and if they are persistent there is already a
configurable rate limiting mechanism available.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-01-19 21:21:13 | pgsql: Fix pg_regress breakage for PL and contrib tests, by not |
| Previous Message | Tom Lane | 2007-01-19 18:34:46 | Re: Windows buildfarm failures |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karen Hill | 2007-01-19 19:43:00 | Re: Planning aggregates which require sorted or distinct input |
| Previous Message | Tom Lane | 2007-01-19 18:34:46 | Re: Windows buildfarm failures |