Skip site navigation (1) Skip section navigation (2)

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: 2006-12-30 21:54:45
Message-ID: 1393.24.211.165.134.1167515685.squirrel@www.dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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



In response to

pgsql-hackers by date

Next:From: Stephen FrostDate: 2006-12-30 21:56:15
Subject: Re: TODO: GNU TLS
Previous:From: Bruce MomjianDate: 2006-12-30 21:48:32
Subject: Re: TODO: GNU TLS

pgsql-patches by date

Next:From: Tom LaneDate: 2006-12-31 05:29:32
Subject: Re: Recent SIGSEGV failures in buildfarm HEAD
Previous:From: Tom LaneDate: 2006-12-30 21:23:02
Subject: Re: [HACKERS] Bundle of patches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group