pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: david@beechglen.com
To: Samuel Hwang <samuel@replicon.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Help! PostgreSQL stuck at starting up after crash
Date: Thu, 19 Jan 2012 11:16:39 -0600
Message-ID: <4F17FB9702000025000449B8@gw.wicourts.gov> (raw)
In-Reply-To: <CAOPCsHFNZAk2Z6zxCKbdPbEnMAHgh0ugTr7sLJxjYPXay1jQ5g@mail.gmail.com>
References: <CAOPCsHHiKKWRAVNFfOUHtuzBW5JLaqQ1KNC_V_J-TamrpuRu=A@mail.gmail.com>
	<c78b6c9b2902d25546465ecb9ea71a12.squirrel@mail.beechglen.com>
	<CAOPCsHFNZAk2Z6zxCKbdPbEnMAHgh0ugTr7sLJxjYPXay1jQ5g@mail.gmail.com>

Samuel Hwang <samuel@replicon.com> wrote:
> I don't know how to make sure if WAL logs corrupted.
> At the end of the recovery in postgresql log I saw
> 
> 2012-01-18 18:30:58.570 MST     3666 - LOG:  consistent recovery
>   state reached at 56C/CD0AFE00
> 2012-01-18 18:30:58.587 MST     3666 - LOG:  recovery stopping
>   before abort of transaction 541802043, time 2012-01-18
>   12:50:08.531615-07
> 2012-01-18 18:30:58.587 MST     3666 - LOG:  redo done at
>   56C/CD226C58
> 2012-01-18 18:30:58.587 MST     3666 - LOG:  last completed
>   transaction was at log time 2012-01-18 12:49:28.321605-07
> 2012-01-18 18:30:58.589 MST     3666 - LOG:  selected new timeline
>   ID: 2
> 2012-01-18 18:30:59.187 MST     3666 - LOG:  archive recovery
>   complete
> 
> just nothing happened after that and postgresql is stuck at
> starting up and not getting out of archive recovery mode.\
 
What do you base that on?  (copy/paste)
 
> at that time there is no cpu/disk activities and it seemed like
> it's waiting for something?
 
That looks like normal recovery.  I would expect it to be waiting
for clients to connect at that point.
 
What happens when you try to connect to the database after that
above has been logged?  (Copy/paste the psql command line and any
errors, please.)
 
-Kevin



view thread (9+ messages)  latest in thread

Message-ID: <4F17FB9702000025000449B8@gw.wicourts.gov>
Permalink:  ../4F17FB9702000025000449B8@gw.wicourts.gov/
Also on:    postgresql.org/message-id/4F17FB9702000025000449B8@gw.wicourts.gov

 · 

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: Kevin.Grittner@wicourts.gov, david@beechglen.com, samuel@replicon.com
  Subject: Re: Help! PostgreSQL stuck at starting up after crash
  In-Reply-To: <4F17FB9702000025000449B8@gw.wicourts.gov>
  References: <CAOPCsHHiKKWRAVNFfOUHtuzBW5JLaqQ1KNC_V_J-TamrpuRu=A@mail.gmail.com> <c78b6c9b2902d25546465ecb9ea71a12.squirrel@mail.beechglen.com> <CAOPCsHFNZAk2Z6zxCKbdPbEnMAHgh0ugTr7sLJxjYPXay1jQ5g@mail.gmail.com> <4F17FB9702000025000449B8@gw.wicourts.gov>

* 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