| 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>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Backup history file should be replicated in Streaming Replication? |
| Date: | 2009-12-22 19:09:59 |
| Message-ID: | 1261508999.7442.7215.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2009-12-22 at 14:02 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > The backup history file is a slightly bit quirky way of doing things and
> > was designed when the transfer mechanism was file-based.
>
> > Why don't we just write a new xlog record that contains the information
> > we need?
>
> Certainly not. The history file is, in the restore-from-archive case,
> needed to *find* the xlog data.
>
> However, it's not clear to me why SR should have any need for it.
> It's not doing restore from archive.
Definitely should not make this *just* in WAL, files still required,
agreed.
It's needed to find the place where the backup stopped, so it defines
the safe stopping point. We could easily pass that info via WAL, when
streaming. It doesn't actually matter until we try to failover.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2009-12-22 19:15:11 | Re: Backup history file should be replicated in Streaming Replication? |
| Previous Message | David Fetter | 2009-12-22 19:09:43 | Re: alpha3 release schedule? |