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

From Thomas F.O'Connell
Subject Safely Killing Backends (Was: Applications that leak connections)
Date
Msg-id eb4b3ca57245296ca64ab678ea560906@sitening.com
Whole thread Raw
In response to Re: Applications that leak connections  (Neil Conway <neilc@samurai.com>)
Responses Re: Safely Killing Backends (Was: Applications that leak connections)
List pgsql-general
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).

-tfo

--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005

On Feb 4, 2005, at 1:57 AM, Neil Conway wrote:

> Paul Tillotson wrote:
>> Does anyone know a safe way to shutdown just one backend
>
> Sending it a SIGTERM via kill(1) should be safe.
>
> -Neil


pgsql-general by date:

Previous
From: "Andrew L. Gould"
Date:
Subject: Fwd: Re: Updating a table on local machine from remote linux server
Next
From: Alvaro Herrera
Date:
Subject: Re: Safely Killing Backends (Was: Applications that leak connections)