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.)
-Kevin