Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 506CE2E0042 for ; Tue, 25 Mar 2008 14:59:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 48228-06 for ; Tue, 25 Mar 2008 14:59:16 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.179]) by postgresql.org (Postfix) with ESMTP id 8C5182E005F for ; Tue, 25 Mar 2008 14:59:18 -0300 (ADT) Received: by el-out-1112.google.com with SMTP id z25so2009692ele.0 for ; Tue, 25 Mar 2008 10:59:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=leGjiyuHvwSjJrVb8zZpX+EsWPDzT82VFpuJXeLv7Xk=; b=KoksmDsRQrDSE1pQVR56X/XYOwxXdTLPXA1QyVke4CgLENoUMScNxScxMga/RDqWVqJ1otzkmjqL1ZLkI968B/jAMBLd3r0zKVvWECNesDN+DKUSsalSnq8gl8UEORaqLJB3UhZV0DOrp75ikcCPUKQal5p4/xAQC62FU2o6ypI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EAWFz0EFwt4H8EyZbTNyqd38wdsGfAjY2hgSXHWdHWfAd5EX5FHjN2Gi9Qb2n81UGVE+ia/qv1f8aN/ZG17eo4zgx/mFxYPQ+9v6gFPLOCMqf2jke1ls39qUiERzPFHyI0EJbgcBdar4cVLi1BkP/Cz2bDRCmD+/UcKWha4ecCA= Received: by 10.141.115.6 with SMTP id s6mr3587541rvm.47.1206467957374; Tue, 25 Mar 2008 10:59:17 -0700 (PDT) Received: by 10.140.139.18 with HTTP; Tue, 25 Mar 2008 10:59:17 -0700 (PDT) Message-ID: <4544e0330803251059v57938d71q68e41cacda057160@mail.gmail.com> Date: Tue, 25 Mar 2008 12:59:17 -0500 From: "Peter Koczan" To: "Tena Sakai" Subject: Re: it refuses to go down... Cc: "Scott Marlowe" , pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/216 X-Sequence-Number: 28699 > > did you try pg_ctl -m immediate stop ??? > > I just did, and it worked. > > $ pg_ctl stop -m immediate > waiting for server to shut down.... done > server stopped I'd be careful about shutting down using "immediate" mode. It forces the database into recovery mode. Your problem could be that one or two connections are in a weird state and even "fast" stopping can't kill them. Next time you have to restart the server, you should check on the status of connections and see if any are in a weird state. I had to deal with this recently where the status was "notify interrupt" and I couldn't even stop fast. I had to change some application code, but not much. Just run "ps ax | grep post" (or whatever options you like to give ps to show all processes) to filter out postgres processes. A connection entry will look like like. [pid] ? Ss 0:00 postgres: [user] [database] [client] [status] Peter