Re: Unkillable Backend Processes - Mailing list pgsql-admin

From Thomas F. O'Connell
Subject Re: Unkillable Backend Processes
Date
Msg-id 6B782E86-0B3E-41BA-B9A9-B7126C2D6989@sitening.com
Whole thread Raw
In response to Re: Unkillable Backend Processes  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-admin
On May 22, 2006, at 8:16 PM, Alvaro Herrera wrote:

> Thomas F. O'Connell wrote:
>
>> When I kill these off individually using kill and then shut down the
>> postmaster with pg_ctl immediate mode, I will occasionally find a
>> backend process that cannot be killed, even with a KILL (-9) signal.
>>
>> Is this likely to be caused by something at a lower level than
>> postgres?
>
> Nothing Postgres does is able to block a SIGKILL (-9) signal.  You can
> be certain that it is stuck in a system call, most likely reading
> something from disk.

That's what I thought. Thanks for the confirmation.

--
Thomas F. O'Connell
Database Architecture and Programming
Sitening, LLC

http://www.sitening.com/
3004 B Poston Avenue
Nashville, TN 37203-1314
615-260-0005 (cell)
615-469-5150 (office)
615-469-5151 (fax)

pgsql-admin by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Unkillable Backend Processes
Next
From: Jeff Frost
Date:
Subject: Re: does wal archiving block the current client connection?