| From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | "List pgsql-patches" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Recent SIGSEGV failures in buildfarm HEAD |
| Date: | 2006-12-30 21:54:45 |
| Message-ID: | 1393.24.211.165.134.1167515685.squirrel@www.dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Stefan Kaltenbrunner wrote:
> Tom Lane wrote:
>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>> ... And then we'd need to change the regression makefile to use
>>> the option, based on an environment variable a bit like
>>> MAX_CONNEXCTIONS
>>> maybe.
>>
>> Why wouldn't we just use it always? If a regression test dumps core,
>> that's going to deserve investigation.
>
> enabling it always for the regression tests probably makes sense - but
> there is also the possibility that such a core can get very large and
> potentially run the partitition the regression test runs on out of space.
>
>
I think Tom is right. You can always set the hard limit before calling
"make check" or running the buildfarm script. I'll prepare a patch to use
similar code unconditionally in pg_regress.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2006-12-30 21:56:15 | Re: TODO: GNU TLS |
| Previous Message | Bruce Momjian | 2006-12-30 21:48:32 | Re: TODO: GNU TLS |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-12-31 05:29:32 | Re: Recent SIGSEGV failures in buildfarm HEAD |
| Previous Message | Tom Lane | 2006-12-30 21:23:02 | Re: [HACKERS] Bundle of patches |