From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Gabi Julien <gabi(dot)julien(at)broadsign(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: New 8.4 hot standby feature |
Date: | 2009-01-27 17:58:47 |
Message-ID: | b42b73150901270958y7cd4e509oef9036f206a4ce9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1/27/09, Gabi Julien <gabi(dot)julien(at)broadsign(dot)com> wrote:
> I have merged the last hot standby patch (v9g) to 8.4 devel and I am pleased
> with the experience. This is promising stuff. Perhaps it is a bit too soon to
> ask questions here but here it is:
>
> 1. Speed of recovery
>
> With a archive_timeout of 60 seconds, it can take about 4 minutes before I see
> the reflected changes in the replica. This is normal since, in addition to
> the WAL log shipping, it takes more time to do the recovery itself. Still, is
> there any way besides the archive_timeout config option to speed up the
> recovery of WAL logs on the hot standby?
you can manually throw pg_switch_xlog(), In practice, this is more of
an issue on development boxes than anything if you server is at all
busy.
see: http://developer.postgresql.org/pgdocs/postgres/functions-admin.html
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2009-01-27 18:08:09 | Re: New 8.4 hot standby feature |
Previous Message | justin | 2009-01-27 17:57:20 | compiling libpq.lb into qsqlpsql.dll |