Re: Recovery control functions

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Recovery control functions
Date: 2011-01-14 12:00:07
Message-ID: 1295006407.12442.58.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2011-01-14 at 12:41 +0100, Magnus Hagander wrote:
> 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?

You can already do that for timestamps.

What you can't do is dynamically set recovery targets via functions,
since currently that is set via recovery.conf parameters. Which requires
restart.

Jaime has a separate patch about recovery targets as well, which does
some more of what you want.

Some things are straightforward, some things require overhaul of the
recovery.conf mechanisms, which is not the right time to do that, nor
have we even discussed let alone agreed what we would change it to.

--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-01-14 12:01:07 Re: Recovery control functions
Previous Message Heikki Linnakangas 2011-01-14 11:47:39 Re: Recovery control functions