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 2BF0B9DCB67 for ; Tue, 14 Mar 2006 16:12:22 -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 07944-08 for ; Tue, 14 Mar 2006 16:12:22 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id D19FF9DCB63 for ; Tue, 14 Mar 2006 16:12:19 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Tue, 14 Mar 2006 20:12:20 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 14 Mar 2006 14:12:20 -0600 Subject: Re: Postgres process terminating From: Scott Marlowe To: Guido Barosio Cc: Cory Vokey , pgsql-admin@postgresql.org In-Reply-To: References: <68df54b40603140654j320d4298hc3cfca58f7993039@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1142367140.2087.29.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 14 Mar 2006 14:12:20 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.148 required=5 tests=[AWL=0.147, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.148 X-Spam-Level: X-Archive-Number: 200603/117 X-Sequence-Number: 20874 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.