| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 07:43:47 |
| Message-ID: | AANLkTik7Egmb725o9Wu7UGNuZgodcnmMBetUrvVxjb9k@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Aug 12, 2010 at 4:18 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> The safest approach is to
>
> 1. run pg_start_backup() on master, remember LSN
> 2. copy backup_label from master to standby
> 3. wait for starting LSN to be applied on standby
ISTM we should wait for the latest checkpoint redo location to reach
the starting location which pg_start_backup() returns.
> That ensures we don't run without full page writes during backup and
> that we have an explicit consistency point to work from.
Yeah, the current documented procedure might not work when
full_page_writes is off on the master. This should be documented.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Valentine Gogichashvili | 2010-08-12 08:33:58 | Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes |
| Previous Message | Fujii Masao | 2010-08-12 07:29:57 | Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes |