| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, 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:18:06 |
| Message-ID: | 1281597486.2142.2061.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, 2010-08-12 at 01:31 -0400, Tom Lane wrote:
> So the DBA is
> just flying blind as to whether the slave is trustworthy yet. I can't
> prove that that's what burnt the original complainant, but it fits the
> symptoms.
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
4. run backup on standby
5. run pg_stop_backup() on master
That ensures we don't run without full page writes during backup and
that we have an explicit consistency point to work from.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2010-08-12 07:29:57 | Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes |
| Previous Message | Tom Lane | 2010-08-12 05:31:57 | Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes |