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 244DB9DCC36 for ; Tue, 14 Mar 2006 16:17:25 -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 09250-04 for ; Tue, 14 Mar 2006 16:17:24 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.195]) by postgresql.org (Postfix) with ESMTP id 1FD539DCC58 for ; Tue, 14 Mar 2006 16:17:21 -0400 (AST) Received: by uproxy.gmail.com with SMTP id h2so807337ugf for ; Tue, 14 Mar 2006 12:17:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rOSAdSlKFgAOsNdCsGnMlo5I6w8rwk9RuAneZZBThJxjhIgsIE8ap4sWL+KUKSJi+Z0cQFSdCRid8Fs0aepph67RgPsObRHjF+GUjQOMh4j+KJw3TuuObeYxDrEpG2+fLiSGOrDnzbMbPt48C3VvCDVN8EtgRpQm/B3RCBmZSh8= Received: by 10.67.20.16 with SMTP id x16mr4717292ugi; Tue, 14 Mar 2006 12:17:23 -0800 (PST) Received: by 10.67.27.10 with HTTP; Tue, 14 Mar 2006 12:17:23 -0800 (PST) Message-ID: Date: Tue, 14 Mar 2006 20:17:23 +0000 From: "Guido Barosio" To: "Scott Marlowe" Subject: Re: Postgres process terminating Cc: "Cory Vokey" , pgsql-admin@postgresql.org In-Reply-To: <1142367140.2087.29.camel@state.g2switchworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <68df54b40603140654j320d4298hc3cfca58f7993039@mail.gmail.com> <1142367140.2087.29.camel@state.g2switchworks.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.218 required=5 tests=[AWL=0.218] X-Spam-Score: 0.218 X-Spam-Level: X-Archive-Number: 200603/118 X-Sequence-Number: 20875 Indeed, from the pg_ctl man pages: ``Immediate'' mode will abort all server processes without a clean shutdown. This will lead to a recovery run on restart. Regards, Guido Barosio On 3/14/06, Scott Marlowe wrote: > On Tue, 2006-03-14 at 14:05, Guido Barosio wrote: > > Hi Cory, > > > > Actually it seems that the database wasn't shut down properly, and > > while it was doing the recovery, it refused connections. Expected and > > what needs to happen, indeed. > > > > That's why if you are a client about to connect, you'll recieve the " > > FATAL ...database is starting up " message. > > > > Ideally, you (the dba) should let the server end this task (the > > recovery). AFAIK, the recovery started as a consecuence of dirty data > > somewere, probably a big transaction not comitted when the server went > > off. > > > > Are you aware of a shutdown prior to this messages? > > > > Nothing to do with your current issue, but you will receive comments > > related with your pgsql version if you are not using a pgsql 8 :) > > As mentioned, this is normal operation. > > Note that the command: > > pg_ctl -m immediate stop > > will cause a recovery. It's pretty much a functional equivalent of > senting kill -9 to all backends and the postmaster at once. Brutal but > effective. > -- /"\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ -----------------------------------------------------------------