Stopping during recovery

This is a multi-part message in MIME format.

------=_NextPart_000_006B_01CACA7A.956733F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi, I've successfully set up a slave system using WAL archiving and =
pg_standby, but I have a couple of questions.

I have a couple of questions:

Is it possible to stop the database server (for maintenance for example) =
and resume the recovery without starting afresh and making a complete =
backup of the original again?
Secondly is it possible to start the database in "readonly" (using set =
default_transaction_read_only) and make a query before resuming the =
recovery?

Thanks

John
--

Got needs? Get Goblin'! - http://www.pricegoblin.co.uk/

------=_NextPart_000_006B_01CACA7A.956733F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



charset=3Diso-8859-1">

Re: Stopping during recovery

--0016e6d99ead2b2a1604827674e0
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Mar 23, 2010 at 7:18 AM, John Lister
wrote:

> Hi, I've successfully set up a slave system using WAL archiving and
> pg_standby, but I have a couple of questions.
>
> I have a couple of questions:
>
> Is it possible to stop the database server (for maintenance for example)
> and resume the recovery without starting afresh and making a complete backup
> of the original again?
>

Yes, it won't begin reading at the very first logfile, it will start based
on your last checkpoint:

http://www.scottrmead.com/blogs/scott/warm-standby-monitorin g
http://www.kennygorman.com/wordpress/?p=249



> Secondly is it possible to start the database in "readonly" (using set
> default_transaction_read_only) and make a query before resuming the
> recovery?
>

No, this feature is only available in 9.0 (which is in alpha) and beyond.

--Scott M

--0016e6d99ead2b2a1604827674e0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable