Message-ID: <47E010C6.8050201@denterprises.org>
Date: Tue, 18 Mar 2008 14:58:14 -0400
From: Colin Wetherbee <cww@denterprises.org>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Chadwick Horn <chadhorn@gmail.com>
CC: pgsql-sql@postgresql.org
Subject: Re: postgres server crashes unexpectedly
References: <71EB10BF787341C28A47F33667D0D8FC@ToshibaLaptop>
	<7206.1205807551@sss.pgh.pa.us>
	<785A9529D52A4C9891401C6DD0A22F24@ToshibaLaptop>
	<25824.1205854526@sss.pgh.pa.us>
	<8ECADC453D394D089097C660876A9BA7@ToshibaLaptop>
In-Reply-To: <8ECADC453D394D089097C660876A9BA7@ToshibaLaptop>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Chadwick Horn wrote:
>> It looks to me like psql is managing to start a new connection 
>> before the postmaster notices the crash of the prior backend and
>>  tells everybody to get out of town.  Which is odd, but maybe not
>>  too implausible if your kernel is set up to favor interactive 
>> processes over background --- it'd likely think psql is 
>> interactive and the postmaster isn't.
> 
> Is there a way to disable this or to make both interactive and/or 
> background?

I'm not sure how applications tell the kernel whether they are
interactive or background (or even if they do, at all), but you can
set the kernel's preference for this in the kernel configuration.

If you're not comfortable recompiling a new kernel, though, then
you're out of luck.

At any rate, you should look more thoroughly for problems with your
database before blaming the kernel for something.

Colin