From: | Keith Fiske <keith(at)omniti(dot)com> |
---|---|
To: | CS_DBA <cs_dba(at)consistentstate(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: HOT standby with ONLY WAL shipping? |
Date: | 2014-06-17 15:48:39 |
Message-ID: | CAG1_KcCtp9-bA6B6Y0ArASOGXOXKyWOweFBoCiXuB5B-=-Ju4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jun 12, 2014 at 1:01 PM, CS_DBA <cs_dba(at)consistentstate(dot)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(at)postgresql(dot)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.
--
Keith Fiske
Database Administrator
OmniTI Computer Consulting, Inc.
http://www.keithf4.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2014-06-17 16:15:49 | Re: How to store fixed size images? |
Previous Message | Ziggy Skalski | 2014-06-17 15:42:39 | Re: pg_restore: custom archiver unexpected end of file , ERROR: missing data for column |