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

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: recovery getting interrupted is not so unusual as it used to be
Date: 2010-05-13 05:28:15
Message-ID: AANLkTimUaoXSfIvrkIsYvTPQYm3MLiuYQCUoMaBj0Uuz@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 13, 2010 at 12:10 PM, Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Takahiro Itagaki 2010-05-13 06:13:03 pg_upgrade code questions
Previous Message Takahiro Itagaki 2010-05-13 05:23:48 Re: Re: [ANNOUNCE] Bug-fix and new feature of pg_lesslog is released