pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Guido Barosio <gbarosio@gmail.com>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Cory Vokey <cvokey@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres process terminating
Date: Tue, 14 Mar 2006 20:17:23 +0000
Message-ID: <f7f6b4c70603141217v33575de1ldfe6bab57adcf1e2@mail.gmail.com> (raw)
In-Reply-To: <1142367140.2087.29.camel@state.g2switchworks.com>
References: <68df54b40603140654j320d4298hc3cfca58f7993039@mail.gmail.com>
	<f7f6b4c70603141205o21020282o8ee32d084cc818a0@mail.gmail.com>
	<1142367140.2087.29.camel@state.g2switchworks.com>

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 <smarlowe@g2switchworks.com> 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 .
/ \ -----------------------------------------------------------------



view thread (5+ messages)  latest in thread

Message-ID: <f7f6b4c70603141217v33575de1ldfe6bab57adcf1e2@mail.gmail.com>
Permalink:  ../f7f6b4c70603141217v33575de1ldfe6bab57adcf1e2@mail.gmail.com/
Also on:    postgresql.org/message-id/f7f6b4c70603141217v33575de1ldfe6bab57adcf1e2@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: gbarosio@gmail.com, smarlowe@g2switchworks.com, cvokey@gmail.com
  Subject: Re: Postgres process terminating
  In-Reply-To: <f7f6b4c70603141217v33575de1ldfe6bab57adcf1e2@mail.gmail.com>
  References: <68df54b40603140654j320d4298hc3cfca58f7993039@mail.gmail.com> <f7f6b4c70603141205o21020282o8ee32d084cc818a0@mail.gmail.com> <1142367140.2087.29.camel@state.g2switchworks.com> <f7f6b4c70603141217v33575de1ldfe6bab57adcf1e2@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox