| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Recovery control functions |
| Date: | 2011-01-14 11:41:16 |
| Message-ID: | AANLkTi=FP+e77TUDGf8tooys+2PyUpeJ5N5DNZYOyUg9@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 14, 2011 at 12:15, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Fri, 2011-01-14 at 11:09 +0000, Simon Riggs wrote:
>> Functions to control recovery, to aid PITR and Hot Standby.
>> pg_is_xlog_replay_paused()
>> pg_xlog_replay_pause()
>> pg_xlog_replay_resume()
>>
>> recovery.conf parameter: pause_at_recovery_target (bool)
Awesome, I've been waiting for these! :-)
How hard would it be to have a pg_xlog_replay_until(<xlog location or
timestamp>), to have it resume recovery up to that point and then
pause again?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-01-14 11:47:39 | Re: Recovery control functions |
| Previous Message | Robert Haas | 2011-01-14 11:40:07 | Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements. |