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 AANLkTimUaoXSfIvrkIsYvTPQYm3MLiuYQCUoMaBj0Uuz@mail.gmail.com
Whole thread Raw
In response to Re: 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 12:10 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> 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?

No. When shutdown happens before reaching consistency, the database might
be inconsistent, but which doesn't mean that some data might be corrupted.
We can get consistent (not corrupted) database by applying the WAL records
to inconsistent one.

> HINT:  If this has occurred more than once some data might be
> corrupted and you might need to choose an earlier recovery target.

I think that the hint message indicates the data corruption which prevents
recovery from completing, rather than the inconsistency of the database.

Regards,

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


pgsql-hackers by date:

Previous
From: Takahiro Itagaki
Date:
Subject: Re: Re: [ANNOUNCE] Bug-fix and new feature of pg_lesslog is released
Next
From: Takahiro Itagaki
Date:
Subject: pg_upgrade code questions