Re: Controlling hot standby

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, devrim(at)gunduz(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Controlling hot standby
Date: 2009-01-23 18:58:15
Message-ID: 1232737095.2327.1276.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Fri, 2009-01-23 at 12:17 -0600, Kevin Grittner wrote:
> >>> Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
> > There are considerable benefits to having it turned on during PITR
> >
> > Please read this to see why
> >
> http://wiki.postgresql.org/wiki/Hot_Standby#Dynamic_Control_of_Recovery
>
> Am I reading this right? What I get out of it is that users can
> connect to the database during recovery, like with psql or JDBC? Any
> user can query recovery completion status and progress, while a
> superuser can also step through transactions in various ways? Can the
> data in the database be queried while recovery is paused?

That's a big Yes to all of that. Exactly what all this is for.

> If I'm understanding this, and data can be queried during a pause, I
> can certainly see use cases for this; but it might be important to be
> able to start the recovery in a paused state to avoid going too far in
> the transaction stream before a connection can be established and
> recovery paused.

OK, that's a simple addition. Thanks for the suggestion.

I'll make it pause just after it changes state, so you can connect and
tell it to progress as far as you like.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2009-01-23 19:17:11 Re: Hot Standby (v9d)
Previous Message Simon Riggs 2009-01-23 18:51:21 Re: Hot Standby (v9d)