> 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)
==> I have waited for at least 2 hours, but the database is still in
starting up state. In the mean time, there is not cpu/disk activities.
> 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
==> when I tried to use psql to connect the db, I got
FATAL: the database system is starting up
and it doesn't allow connection.
On Thu, Jan 19, 2012 at 10:16 AM, Kevin Grittner <
> Samuel Hwang <samuel(at)replicon(dot)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.)
*Shian-Miin Samuel Hwang* | Software Developer | Phone 1-403-2626519 (ext.
276) | Fax 1-403-233-8046
*Replicon* | Hassle-Free Time & Expense Management Software - 7,300
Customers - 70 Countries
www.replicon.com | facebook <http://www.facebook.com/Replicon.inc> |
blog <http://www.replicon.com/blog/> | contact
*We are hiring!* | search
In response to
pgsql-admin by date
|Next:||From: Samuel Hwang||Date: 2012-01-19 22:45:34|
|Subject: Re: Help! PostgreSQL stuck at starting up after crash|
|Previous:||From: Bruce Momjian||Date: 2012-01-19 22:12:02|
|Subject: Re: Can't get pg_upgrade work for 8.4|