From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Guido Barosio <gbarosio(at)gmail(dot)com> |
Cc: | Cory Vokey <cvokey(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Postgres process terminating |
Date: | 2006-03-14 20:12:20 |
Message-ID: | 1142367140.2087.29.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Guido Barosio | 2006-03-14 20:17:23 | Re: Postgres process terminating |
Previous Message | Guido Barosio | 2006-03-14 20:05:53 | Re: Postgres process terminating |