Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: valgog <valgog(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes
Date: 2010-08-12 05:15:08
Message-ID: AANLkTi=a4pyk2uUNG5LAKoumkjiOjZuD4n3_RV8Q1jHD@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Aug 6, 2010 at 7:50 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> The procedure used does differ from that documented. However, IMHO the
> procedure *documented* is *not* safe and could lead to corrupt indexes
> in the way described, since the last recovered point might be mid-way
> between two halves of an index split record, which will never be
> corrected during HS.

An index split record is replayed by two calls of rm_redo()? If not,
we don't need to worry about the above since the last recovered point
which pg_last_xlog_replay_location() returns is updated after every
rm_redo().

Regards,

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-08-12 05:31:57 Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes
Previous Message Robert Haas 2010-08-12 00:28:03 Re: BUG #5588: I use a lot of the "INHERITS", results of tests found that the performance is very low.