X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 622D79DCB82 for ; Fri, 3 Feb 2006 00:47:25 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 71881-01 for ; Fri, 3 Feb 2006 00:47:23 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 260789DCBBB for ; Fri, 3 Feb 2006 00:47:21 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k134lKkd022803; Thu, 2 Feb 2006 23:47:20 -0500 (EST) To: Jeremy Ashcraft cc: pgsql-admin@postgresql.org Subject: Re: strange hung processes In-reply-to: <43E26A23.1080208@edgate.com> References: <43E26A23.1080208@edgate.com> Comments: In-reply-to Jeremy Ashcraft message dated "Thu, 02 Feb 2006 12:22:59 -0800" Date: Thu, 02 Feb 2006 23:47:20 -0500 Message-ID: <22802.1138942040@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.103 required=5 tests=[AWL=0.103] X-Spam-Score: 0.103 X-Spam-Level: X-Archive-Number: 200602/31 X-Sequence-Number: 20452 Jeremy Ashcraft writes: > in /proc > codd 13262 # cat status {proc "filesystem"} > Name: postmaster > State: D (disk sleep) > Because of the "D" state, it can't be killed as it is not interuptible > (waiting on IO ?). If the process is stuck in D state then it's not Postgres' fault. You're looking at a hardware problem, or if the database is mounted via NFS then it might be an NFS-protocol-level problem. In any case you need to call out the kernel and hardware troops, not us database weenies ... regards, tom lane