Re: streamlined standby procedure - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: streamlined standby procedure
Date
Msg-id e51f66da0602090644k75e5c37w24097d41983b8e5c@mail.gmail.com
Whole thread Raw
In response to Re: streamlined standby procedure  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: streamlined standby procedure
List pgsql-hackers
On 2/7/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andrew Rawnsley <ronz@investoranalytics.com> writes:
> > IMHO the #1 priority in the current PITR/WAL shipping system is to make the
> > standby able to tolerate being shut down and restarted, i.e. actually having
> > a true standby mode and not the current method of doing it only on startup.
>
> How is shutting down the standby a good idea?  Seems like that will
> block the master too --- or at least result in WAL log files piling up
> rapidly.  If the standby goes off-line, abandoning it and starting from
> a fresh base backup when you are ready to restart it seems like the most
> likely recovery path.  For sure I don't see this as the "#1 priority".

For regular recovery it is indeed unnecessary.  But I would also
put this as #1 TODO for long-running hot-standby case.  The requirement
to start all over makes current setup rather cumbersome.

And #2 would be running read-only queries while in recovery :)

--
marko


pgsql-hackers by date:

Previous
From: "Mark Woodward"
Date:
Subject: PostgreSQL 8.0.6 crash
Next
From: "Premnath, KN"
Date:
Subject: {I} One Information required...