Re: recovery getting interrupted is not so unusual as it used to be - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: recovery getting interrupted is not so unusual as it used to be
Date
Msg-id AANLkTimvKL_Q_mEr8FoOqGOIUkpBh9-Sz9bSyqPcVaKs@mail.gmail.com
Whole thread Raw
In response to recovery getting interrupted is not so unusual as it used to be  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: recovery getting interrupted is not so unusual as it used to be
List pgsql-hackers
On Thu, May 13, 2010 at 10:01 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> When firing up a properly shut down HS slave, I get:
>
> LOG:  database system was interrupted while in recovery at log time
> 2010-05-12 20:35:24 EDT
> HINT:  If this has occurred more than once some data might be
> corrupted and you might need to choose an earlier recovery target.
>
> But this is kind of an alarming hint for what is now a normal and
> expected condition.  Can we detect the difference between the case
> where the HINT is really accurate and the case where it's not in some
> way, and display a better message?

How about my previous proposal: adding new system status like
DB_SHUTDOWNED_IN_RECOVERY, setting the status to it when the shutdown
is performed during recovery, and reporting the suitable message
when starting up the server from it?
http://archives.postgresql.org/pgsql-hackers/2010-02/msg00337.php

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: comment needs to be updated for HS?
Next
From: Robert Haas
Date:
Subject: Re: max_standby_delay considered harmful