| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Backup history file should be replicated in Streaming Replication? |
| Date: | 2009-12-24 08:38:24 |
| Message-ID: | 3f0b79eb0912240038i7bbd284bt186a0856fbd2bcc1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 24, 2009 at 1:39 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Wed, Dec 23, 2009 at 7:50 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> Ok. How about writing the history file in pg_stop_backup() for
>> informational purposes only. Ie. never read it, but rely on the WAL
>> records instead.
>
> Sounds good. I'll make such change as a self-contained patch.
Done. Please see the attached patch.
Design:
* pg_stop_backup writes the backup-end xlog record which contains
the backup starting point.
* In archive recovery, the startup process doesn't mark the database
as consistent until it has read the backup-end record.
* A backup history file is still created as in the past, but is never
used.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| Attachment | Content-Type | Size |
|---|---|---|
| backup_end_xlog_record.patch | text/x-patch | 12.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2009-12-24 08:53:53 | Re: Backup history file should be replicated in Streaming Replication? |
| Previous Message | Simon Riggs | 2009-12-24 08:35:29 | Re: Backup history file should be replicated in Streaming Replication? |