X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6286553482 for ; Tue, 19 Apr 2005 11:57:53 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 10733-06 for ; Tue, 19 Apr 2005 14:57:46 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 80C55533A8 for ; Tue, 19 Apr 2005 11:57:46 -0300 (ADT) 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 j3JEvnEJ021643; Tue, 19 Apr 2005 10:57:49 -0400 (EDT) To: Rolf Staege Cc: pgsql-admin@postgresql.org Subject: Re: postmaster hangs In-reply-to: <426517F4.1040603@med.uni-rostock.de> References: <426517F4.1040603@med.uni-rostock.de> Comments: In-reply-to Rolf Staege message dated "Tue, 19 Apr 2005 16:38:44 +0200" Date: Tue, 19 Apr 2005 10:57:49 -0400 Message-ID: <21642.1113922669@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/266 X-Sequence-Number: 17279 Rolf Staege writes: > i'm using postgres version 7.4.1 and it run very stable until, may be, > 4 weeks ago. > now the postmaster hangs sometimes for a while (actually since 2 hours) > and doesn't accept connections but comes back anytime. there is no > possibility to stop the postmaster. even a kill -9 (it's only the > developement system) doesn't work. i have to reboot the system to get > the database running again. Hardware problems? Most of the cases I've heard of where kill -9 didn't work, it was because the process was partway through a disk operation and the kernel was holding off the signal until the I/O completed ... but there was something broken about the disk and so the operation never completed. In any case, there is *no* way for an unprivileged process like Postgres to resist kill -9, so your problem is certainly at either the hardware or kernel level. I'd suggest talking to HP ... regards, tom lane