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 7AAB85408C for ; Sun, 24 Apr 2005 13:02:15 -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 96122-04 for ; Sun, 24 Apr 2005 16:02:13 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 99B5F5405A for ; Sun, 24 Apr 2005 13:02:12 -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 j3OG292v007016; Sun, 24 Apr 2005 12:02:09 -0400 (EDT) To: "Simpson" Cc: pgsql-admin@postgresql.org Subject: Re: postmaster stop hangs In-reply-to: References: Comments: In-reply-to "Simpson" message dated "Sun, 24 Apr 2005 07:54:50 -0500" Date: Sun, 24 Apr 2005 12:02:09 -0400 Message-ID: <7015.1114358529@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/355 X-Sequence-Number: 17368 "Simpson" writes: > Here is a ps of the currently running instance: > postgres 5671 1 0 02:32 pts/0 00:00:00 > /usr/local/pgsql/bin/postmaster -D /data/pgsql/data > postgres 5674 5671 0 02:32 pts/0 00:00:00 postgres: writer process > postgres 5675 5671 0 02:32 pts/0 00:00:00 postgres: stats buffer > process > postgres 5676 5675 0 02:32 pts/0 00:00:00 postgres: stats collector > process > 5676 is in the */data/postmaster.pid That seems extremely broken. Can you reproduce this state (wrong PID in postmaster.pid) after restarting the postmaster? regards, tom lane