Re: Unkillable Backend Processes

From: "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Unkillable Backend Processes
Date: 2006-05-23 01:24:10
Message-ID: 6B782E86-0B3E-41BA-B9A9-B7126C2D6989@sitening.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Jeff Frost 2006-05-23 03:59:30 Re: does wal archiving block the current client connection?
Previous Message Alvaro Herrera 2006-05-23 01:16:10 Re: Unkillable Backend Processes