Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 36F26476481 for ; Wed, 5 Jun 2002 13:11:20 -0400 (EDT) Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (Postfix) with ESMTP id 31A614764A6 for ; Wed, 5 Jun 2002 12:33:45 -0400 (EDT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g55GXm718101; Wed, 5 Jun 2002 12:33:48 -0400 (EDT) From: Bruce Momjian Message-Id: <200206051633.g55GXm718101@candle.pha.pa.us> Subject: Re: Further info : Very high load average but no cpu utilization In-Reply-To: <20020513102120.6BB3C1AFD@druid.net> To: pgsql-sql@postgresql.org Date: Wed, 5 Jun 2002 12:33:48 -0400 (EDT) Cc: "Rajesh Kumar Mallah." , Tom Lane X-Mailer: ELM [version 2.4ME+ PL97 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200206/38 X-Sequence-Number: 8003 D'Arcy J.M. Cain wrote: > On May 13, 2002 12:50 am, Rajesh Kumar Mallah. wrote: > > Its advocated "dont kill -9 the postmaster" and i rarely do that. > > Advocated or not, kill -9 is supposed to be the last resort. If nothing else > works then kill -9 should kill any Unix process. As Tom says, if it doesn't > then it suggests an OS (probably driver) problem. > > Now if only I could get IBM to understand that. They still claim that my > problem is that PostgreSQL (an "unsupported" application) is doing something > to catch SIGKILL. First, an application can't catch SIGKILL. It never arrives to applications. It is supposed to pull the process with no warning. However, there are things processes can do to wedge themselves in a system call so they don't see the SIGKILL. Of course, as soon as they return from the system call, they die. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026