Safely Killing Backends (Was: Applications that leak connections)

From: Thomas F(dot)O'Connell <tfo(at)sitening(dot)com>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Paul Tillotson <pntil(at)shentel(dot)net>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Safely Killing Backends (Was: Applications that leak connections)
Date: 2005-02-04 19:44:10
Message-ID: eb4b3ca57245296ca64ab678ea560906@sitening.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2005-02-04 19:56:12 Re: Safely Killing Backends (Was: Applications that leak connections)
Previous Message Andrew L. Gould 2005-02-04 19:41:18 Fwd: Re: Updating a table on local machine from remote linux server