Re: HOT standby with ONLY WAL shipping?
| От | Keith Fiske |
|---|---|
| Тема | Re: HOT standby with ONLY WAL shipping? |
| Дата | |
| Msg-id | CAG1_KcCtp9-bA6B6Y0ArASOGXOXKyWOweFBoCiXuB5B-=-Ju4A@mail.gmail.com обсуждение исходный текст |
| Ответ на | HOT standby with ONLY WAL shipping? (CS_DBA <cs_dba@consistentstate.com>) |
| Список | pgsql-general |
On Thu, Jun 12, 2014 at 1:01 PM, CS_DBA <cs_dba@consistentstate.com> wrote:
Hi All;
We would like to setup a hot standby server with a forced delay.
Is it possible to setup a hot standby based ONLY on WAL shipping and NOT use streaming replication?
Thanks in advance
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
The omnipitr tool can provide the delayed slave feature you're looking for.
https://github.com/omniti-labs/omnipitr/
Look into the --recovery-delay (-w) feature of the omnipitr-restore command which is used in the recovery.conf of the slave
https://github.com/omniti-labs/omnipitr/blob/master/doc/omnipitr-restore.pod
Whether a slave is a hot standby is not determined by whether you're using streaming replication or WAL replay. It is determined by setting the parameter "hot_standby" on the slave and ensuring the master has a minimum "wal_level" of "hot_standby" as well. So both streaming and wal replay slaves can be hot standbys.https://github.com/omniti-labs/omnipitr/
Look into the --recovery-delay (-w) feature of the omnipitr-restore command which is used in the recovery.conf of the slave
https://github.com/omniti-labs/omnipitr/blob/master/doc/omnipitr-restore.pod
В списке pgsql-general по дате отправления: