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 BE8B49DC820 for ; Fri, 20 Jan 2006 11:48:55 -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 96001-01 for ; Fri, 20 Jan 2006 11:48:59 -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 E977E9DC87D for ; Fri, 20 Jan 2006 11:48:52 -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 k0KFmuXC017592; Fri, 20 Jan 2006 10:48:56 -0500 (EST) To: Christian Sengstock cc: pgsql-admin@postgresql.org Subject: Re: problem with dead 'drop table' process In-reply-to: References: Comments: In-reply-to Christian Sengstock message dated "Fri, 20 Jan 2006 15:27:08 +0100" Date: Fri, 20 Jan 2006 10:48:56 -0500 Message-ID: <17591.1137772136@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.094 required=5 tests=[AWL=0.094] X-Spam-Score: 0.094 X-Spam-Level: X-Archive-Number: 200601/238 X-Sequence-Number: 20326 Christian Sengstock writes: > to save the database on a filesystem basis i stopped the postgres server and > tried to tar the entire pgdata directory. this process stopped with a > "segmentation fault" during the tar process. So there's something wrong beyond just postgres ... > the server is running, and i can connect with another psql client, but the > drop table process is still present. ps aux shows > postgres 5548 0.0 0.8 16420 4548 ? D 07:58 0:00 postgres: postgres > wlan [local] DROP TABLE > i cannot kill it with kill -9, and also i'm not sure if i should. maybe the > database is not running after it at all? A process stuck in an unkillable disk wait is a pretty common symptom of low-level problems. There might be a disk hardware issue --- have you looked into the kernel message log on the machine? regards, tom lane