From: | Marko Kreen <markokr(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Rawnsley <ronz(at)investoranalytics(dot)com>, postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: streamlined standby procedure |
Date: | 2006-02-09 14:44:20 |
Message-ID: | e51f66da0602090644k75e5c37w24097d41983b8e5c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/7/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Rawnsley <ronz(at)investoranalytics(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Woodward | 2006-02-09 15:10:06 | PostgreSQL 8.0.6 crash |
Previous Message | Andrew Dunstan | 2006-02-09 14:41:33 | Re: User Defined Types in Java |