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 0CED79DC89C for ; Tue, 14 Mar 2006 22:31:09 -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 70274-03 for ; Tue, 14 Mar 2006 22:31:12 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by postgresql.org (Postfix) with ESMTP id DB07A9DC838 for ; Tue, 14 Mar 2006 22:31:06 -0400 (AST) Received: by zproxy.gmail.com with SMTP id s1so15585nze for ; Tue, 14 Mar 2006 18:31:10 -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:references; b=q8r8qhLftgSArSaqld1RpP3fYGssk/+04TwZDBoY2GiN2MEZ1LMLS4mJ77dSxVDxwTy4Rc0hpQpWt91pUNpiCk9ggJ2Hx6iCwNhvyX+npJ88fapb/zwjFjjbCYL9G6qIXWdYjOV6oZtDWyF/LKjiPPEYip/kPAp1uK5MJQKZ5uE= Received: by 10.36.247.27 with SMTP id u27mr32384nzh; Tue, 14 Mar 2006 18:31:10 -0800 (PST) Received: by 10.36.196.7 with HTTP; Tue, 14 Mar 2006 18:31:10 -0800 (PST) Message-ID: <68df54b40603141831o593b46e8te81d2dab811c5d94@mail.gmail.com> Date: Tue, 14 Mar 2006 20:31:10 -0600 From: "Cory Vokey" To: "Guido Barosio" Subject: Re: Postgres process terminating Cc: "Scott Marlowe" , pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_999_2862831.1142389870301" 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.593 required=5 tests=[AWL=0.592, HTML_MESSAGE=0.001] X-Spam-Score: 0.593 X-Spam-Level: X-Archive-Number: 200603/121 X-Sequence-Number: 20878 ------=_Part_999_2862831.1142389870301 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 3/14/06, Guido Barosio wrote: > > 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 wen= t > > > 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 . > / \ ----------------------------------------------------------------- > Ok, thanks a lot guys. It seems that I should have brought the database down to "local access" mod= e via pg_hba.conf and allow all transactions to fully recover before starting up replication or allowing other applications to access the db. Have a good night all! -- Cory Vokey ------=_Part_999_2862831.1142389870301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

On 3/14/06, Guido Barosio <gbarosi= o@gmail.com> wrote:
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:
&= gt; > Hi Cory,
> >
> > Actually it seems that the data= base wasn't shut down properly, and
> > while it was doing the recovery, it refused connections. Expe= cted and
> > what needs to happen, indeed.
> >
> &g= t; That's why if you are a client about to connect, you'll recieve the &quo= t;
> > FATAL ...database is starting up " message.
> >=
> > Ideally, you (the dba) should let the server end this task (t= he
> > recovery). AFAIK, the recovery started as a consecuence of = dirty data
> > somewere, probably a big transaction not comitted when the se= rver went
> > off.
> >
> > Are you aware of a sh= utdown 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 &= nbsp;pgsql 8 :)
>
> As mentioned, this is normal operation.
= >
> Note that the command:
>
> pg_ctl -m immediate sto= p
>
> will cause a recovery.  It's pretty much a functional eq= uivalent of
> senting kill -9 to all backends and the postmaster at o= nce.  Brutal but
> effective.
>


--
/&qu= ot;\   ASCII Ribbon Campaign  .
\ / - NO HTML/RTF in e-mail  .
X  - NO Word doc= s in e-mail .
/ \ ------------------------------------------------------= -----------

Ok, thanks a lot guys. 

It seems that I should have brought the database down to "local access= " mode via pg_hba.conf and allow all transactions to fully recover before starting up replication or allowing other applications to access the db.
Have a good night all!

--
Cory Vokey ------=_Part_999_2862831.1142389870301--