Re: recovery getting interrupted is not so unusual as it used to be

On Wed, May 12, 2010 at 11:07 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Thu, May 13, 2010 at 10:01 AM, Robert Haas <robertmhaas(at)gmail(dot)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

Hmm, it seems this is my night to rediscover the wisdom of your
previous proposals. I think that state would only be appropriate when
we shutdown after reaching consistency, not any shutdown during
recovery. Do you agree?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company