From: Colin Wetherbee <cww@denterprises.org>
To: Chadwick Horn <chadhorn@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: postgres server crashes unexpectedly
Date: Tue, 18 Mar 2008 14:58:14 -0400
Message-ID: <47E010C6.8050201@denterprises.org> (raw)
In-Reply-To: <8ECADC453D394D089097C660876A9BA7@ToshibaLaptop>
References: <71EB10BF787341C28A47F33667D0D8FC@ToshibaLaptop>
<7206.1205807551@sss.pgh.pa.us>
<785A9529D52A4C9891401C6DD0A22F24@ToshibaLaptop>
<25824.1205854526@sss.pgh.pa.us>
<8ECADC453D394D089097C660876A9BA7@ToshibaLaptop>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: cww@denterprises.org, chadhorn@gmail.com
Subject: Re: postgres server crashes unexpectedly
In-Reply-To: <47E010C6.8050201@denterprises.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox