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
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
