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

Re: [HACKERS] Recent SIGSEGV failures in buildfarm HEAD

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, List pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Recent SIGSEGV failures in buildfarm HEAD
Date: 2006-12-29 23:08:56
Message-ID: 4595A008.4000204@kaltenbrunner.cc (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
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.


Stefan

In response to

Responses

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2006-12-29 23:21:50
Subject: Re: TODO: GNU TLS
Previous:From: Robert TreatDate: 2006-12-29 22:57:12
Subject: Re: TODO: GNU TLS

pgsql-patches by date

Next:From: Bruce MomjianDate: 2006-12-30 02:02:11
Subject: Re: Load distributed checkpoint
Previous:From: Tom LaneDate: 2006-12-29 21:44:39
Subject: Re: [HACKERS] Recent SIGSEGV failures in buildfarm HEAD

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