Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-06 03:20:11
Message-ID: 8231.1281064811@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On Thu, 2010-08-05 at 11:28 -0700, valgog wrote:
>> It was done as documented in http://www.postgresql.org/docs/9.0/static/backup-incremental-updated.html

> 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.

Hm, I was looking at that and thinking it seemed unsafe for entirely
different reasons.  But if you didn't write it, who did?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Fujii MasaoDate: 2010-08-06 03:56:45
Subject: Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes
Previous:From: Greg StarkDate: 2010-08-06 02:44:30
Subject: Re: BUG #5599: Vacuum fails due to index corruption issues

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group