Re: Minimizing Recovery Time (wal replication)

Поиск
Список
Период
Сортировка
Искать
От
Koichi Suzuki
Тема
Re: Minimizing Recovery Time (wal replication)
Дата
Msg-id
a778a7260904141749kf1240c4mf8c3c6f086ec8937@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Minimizing Recovery Time (wal replication) Bryan Murphy <bmurphy1976@gmail.com>
Re: Minimizing Recovery Time (wal replication) Simon Riggs <simon@2ndQuadrant.com>
Re: Minimizing Recovery Time (wal replication) Bryan Murphy <bmurphy1976@gmail.com>
Re: Minimizing Recovery Time (wal replication) Koichi Suzuki <koichi.szk@gmail.com>
Re: Minimizing Recovery Time (wal replication) Greg Smith <gsmith@gregsmith.com>
Re: Minimizing Recovery Time (wal replication) Bryan Murphy <bmurphy1976@gmail.com>
Re: Minimizing Recovery Time (wal replication) Greg Smith <gsmith@gregsmith.com>
Re: Minimizing Recovery Time (wal replication) Bryan Murphy <bmurphy1976@gmail.com>
If you're using "full page write = off", prefetching data page from
WAL speeds up the recovery too.  I've proposed this patch but was
carried over to 8.5.   I'm planning to release this as an external
tool, which will not work well  with Hot Standby but will work in
usual recovery.

I'm not sure how soon I can do it but hope it works.

2009/4/13 Bryan Murphy :
> On Sun, Apr 12, 2009 at 5:52 AM, Simon Riggs  wrote:
>> The database is performing too frequent restartpoints.
>>
>> This has been optimised in PostgreSQL 8.4 by the addition of the
>> bgwriter running during recovery. This will mean that your hot spare
>> will not pause while waiting for restartpoint to complete, so will be
>> significantly faster.
>
> 8.4 is already looking like it's going to be a great upgrade for us,
> this would be another win.
>
> Thanks,
> Bryan
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>



-- 
------
Koichi Suzuki
В списке pgsql-general по дате отправления
От: Dan Hayes
Дата:
От: CM J
Дата:
Сообщение: Postgres server startup
FAQ