To: pgsql-admin@postgresql.org
From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Subject: Effect of archive_mode , archive_command when set on the standby
Message-ID: <582F2CE5.6030408@matrix.gatewaynet.com>
Date: Fri, 18 Nov 2016 18:31:33 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Hello,

We are using 9.3.10 on a hot standby, and I am trying to setup cascading replication in order to clone one of our master DBs to the cloud (lifting the heavy burden from the master).
I am noticing that setting archive_mode , archive_command on the hot standby have absolutely zero effect.
Can a standby (re)produce wal files for archiving / purposed for feeding to a downstream standby or is streaming the only way it works?
In the docs (9.3) I didn't find anything regarding those parameters when used on the standby server.

Currently on the master we don't keep a window of wals large enough to contain the activity of that many days as the duration of the cloning of the data disks to the cloud will last. I was thinking if 
we could just leave the master as is with its current (shorter term) archiving settings (3 days), and tweak only this specific hot standby to archive the wals on its own, providing a larger window (7 
days+) for the new downstream standby to catch up before we revert to streaming.

Am I missing anything?

-- 
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin