From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | 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:12 |
Message-ID: | 3f0b79eb0912221109o2f80673fr6853e0fc32f72170@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 23, 2009 at 3:41 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> This means that we can replace a backup history file with the corresponding
>> xlog record. I think that we should simplify the code by making the replacement
>> completely rather than just adding new xlog record. Thought?
>
> We can't do that because it would stop file-based archiving from
> working. I don't think we should deprecate that for another release at
> least.
Umm... ISTM that we can do that even if file-base archiving case;
* pg_stop_backup writes the xlog record corresponding to a backup
history file, and requests the WAL file switch.
* In PITR or warm-standby, the startup process just marks database
as inconsistent until it has read that xlog record.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2009-12-22 19:09:43 | Re: alpha3 release schedule? |
Previous Message | David E. Wheeler | 2009-12-22 19:04:29 | Re: alpha3 release schedule? |