Re: [HACKERS] Recent SIGSEGV failures in buildfarm HEAD
- 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: Sat, 30 Dec 2006 15:54:45 -0600 (CST)
- Message-id: <1393.24.211.165.134.1167515685.squirrel@www.dunslane.net> <text/plain>
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
Home |
Main Index |
Thread Index