Re: Help! PostgreSQL stuck at starting up after crash

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: Help! PostgreSQL stuck at starting up after crash
Дата
Msg-id 4F17FB9702000025000449B8@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: Help! PostgreSQL stuck at starting up after crash  (Samuel Hwang <samuel@replicon.com>)
Ответы Re: Help! PostgreSQL stuck at starting up after crash  (Samuel Hwang <samuel@replicon.com>)
Список pgsql-admin
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

В списке pgsql-admin по дате отправления:

Предыдущее
От: Samuel Hwang
Дата:
Сообщение: Re: Help! PostgreSQL stuck at starting up after crash
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Can't get pg_upgrade work for 8.4