| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Subject: | Re: Archiving control (a part of synch rep patches) |
| Date: | 2008-12-24 10:26:42 |
| Message-ID: | 1230114402.4793.1071.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2008-12-24 at 19:04 +0900, Fujii Masao wrote:
> Hi,
>
> On Wed, Dec 24, 2008 at 4:39 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> > (3)
> > Revert the arhive status file of the specified file from .done to .ready.
> > This would try to archive the corresponding xlog file again. The archive
> > status of only skipped xlog file can be reverted.
> >
> > We resume xlog archiving by using (2) and (3), when replication
> > ends.
>
> Umm.. reverting is very tricky, then it might become hotbeds of bugs.
> So, I will reconsider the method of resuming archive.
Yeh, don't do that.
No worries if we send a few files too many. Tears if we miss just one.
* Turn it off for the *next* file to be archived. Keep track of last
file sent.
* Turn it on again, mark *all* WAL files as .ready in sequence low to
high, as long as they are higher than the last file sent.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2008-12-24 10:38:26 | Re: generic reloptions improvement |
| Previous Message | Pavan Deolasee | 2008-12-24 10:21:11 | Re: Synchronous replication, reading WAL for sending |