Re: Safely Killing Backends (Was: Applications that leak connections) - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Safely Killing Backends (Was: Applications that leak connections)
Date
Msg-id 20050204195612.GA28939@dcc.uchile.cl
Whole thread Raw
In response to Safely Killing Backends (Was: Applications that leak connections)  (Thomas F.O'Connell <tfo@sitening.com>)
Responses Re: Safely Killing Backends (Was: Applications that leak connections)
List pgsql-general
On Fri, Feb 04, 2005 at 01:44:10PM -0600, Thomas F.O'Connell wrote:
> Is there any stronger medicine that's available (for instance, when a
> backend won't respond to SIGTERM) and has no unfortunate side effects?
> I just ran into this situation the other day (and made the unfortunate
> discovery that SIGABRT is as bad as SIGKILL as far as a postmaster is
> concerned).

As soon as a backend dies a unnatural death, postmaster will rightly
consider that it may have corrupted the shared state.  In turn
postmaster will kill all its children mercilessly so they don't spread
the disease.

Even SIGTERM can have bad consequences if it arrives at the wrong time.
(That's why a function to close a remote connection was rejected.)

So, short answer: no.

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"La virtud es el justo medio entre dos defectos" (Aristóteles)

pgsql-general by date:

Previous
From: Thomas F.O'Connell
Date:
Subject: Safely Killing Backends (Was: Applications that leak connections)
Next
From: Thomas F.O'Connell
Date:
Subject: Re: Safely Killing Backends (Was: Applications that leak connections)