From: | "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at> |
---|---|
To: | "Tim Allen *EXTERN*" <tim(at)proximity(dot)com(dot)au> |
Cc: | <pgsql-hackers(at)postgresql(dot)org>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Forcing current WAL file to be archived |
Date: | 2006-08-01 08:38:24 |
Message-ID: | 52EF20B2E3209443BC37736D00C3C13809B5B64C@EXADV1.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tim Allen wrote:
>>>Patch included to implement xlog switching, using an xlog record
>>>"processing instruction" and forcibly moving xlog pointers.
>>>
>>>1. Happens automatically on pg_stop_backup()
>>
>>
>> Oh - so it will not be possible to do an online backup
>> _without_ forcing a WAL switch any more?
>
> Well, previously, you would have always had to simulate a wal
> switch, by
> working out which is the current wal file and copying that. Otherwise
> your online backup wouldn't be complete.
>
> What Simon is describing sounds like a big step forward from that
> situation. It should let me delete half the code in my pitr
> backup/failover scripts. Definitely a Good Thing.
Certainly a Good Thing, and it should be on by default.
But couldn't there be situations where you'd like to do an
online backup without a WAL switch? To avoid generating an
archive WAL every day on a database with few changes, e.g.?
Maybe not, I'm just wondering.
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Florian G. Pflug | 2006-08-01 08:48:20 | Re: [HACKERS] Forcing current WAL file to be archived |
Previous Message | Tim Allen | 2006-08-01 08:27:50 | Re: Forcing current WAL file to be archived |
From | Date | Subject | |
---|---|---|---|
Next Message | Florian G. Pflug | 2006-08-01 08:48:20 | Re: [HACKERS] Forcing current WAL file to be archived |
Previous Message | Tim Allen | 2006-08-01 08:27:50 | Re: Forcing current WAL file to be archived |