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 A654F540A0 for ; Mon, 25 Apr 2005 08:47:34 -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 61968-06 for ; Mon, 25 Apr 2005 11:47:24 +0000 (GMT) Received: from exit1.i-55.com (exit1.i-55.com [208.231.96.22]) by svr1.postgresql.org (Postfix) with ESMTP id 24A5F5408D for ; Mon, 25 Apr 2005 08:47:21 -0300 (ADT) Received: from simpsonnew (dsl-209-205-186-247.i-55.com [209.205.186.247]) by exit1.i-55.com (8.11.7/8.11.4) with SMTP id j3PBlO309385; Mon, 25 Apr 2005 06:47:24 -0500 From: "Simpson" To: "Tom Lane" Cc: Subject: Re: postmaster stop hangs Date: Mon, 25 Apr 2005 06:49:08 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-reply-to: <7015.1114358529@sss.pgh.pa.us> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.07 tagged_above=0 required=5 tests=AWL, DNS_FROM_AHBL_RHSBL X-Spam-Level: X-Archive-Number: 200504/359 X-Sequence-Number: 17372 Yes, it does it consistently. Maybe I should start from scratch, if this seems very broken. Drew. -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Tom Lane Sent: Sunday, April 24, 2005 11:02 AM To: Simpson Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] postmaster stop hangs "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 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match