Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 1446C475E92 for ; Sun, 12 May 2002 11:43:26 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id CEF77475FF0 for ; Sun, 12 May 2002 11:37:46 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g4CFbpW29867; Sun, 12 May 2002 11:37:51 -0400 (EDT) To: pgsql-sql@postgresql.org Cc: "Rajesh Kumar Mallah." Subject: Re: Further info : Very high load average but no cpu utilization ? In-reply-to: <20020512110537.F403E1BBC@druid.net> References: <200205111007.47338.mallah@trade-india.com> <13062.1021132784@sss.pgh.pa.us> <200205121116.30681.mallah@trade-india.com> <20020512110537.F403E1BBC@druid.net> Comments: In-reply-to "D'Arcy J.M. Cain" message dated "Sun, 12 May 2002 07:05:37 -0400" Date: Sun, 12 May 2002 11:37:51 -0400 Message-ID: <29864.1021217871@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200205/114 X-Sequence-Number: 7750 "D'Arcy J.M. Cain" writes: > Not even kill -9 worked? I had that happen too but I thought it was a > problem with AIX. Kill -9 is supposed to kill any process. It can't be > caught. Is it possible that PostgreSQL is doing something that makes it that > unkillable? Could there be a kernel bug associated with processes that are trying to write past the 2Gb limit? The postmaster is certainly not doing anything deliberate to make itself unkillable, but on some platforms kill -9 will not work on processes that are wedged in a system call... regards, tom lane