---------- Forwarded message ----------
From: Michael Nolan <htfoot@xxxxxxxxx>
Date: Tue, May 29, 2012 at 1:37 PM
Subject: Re: Disable Streaming Replication without restarting either master or slave
To: Fujii Masao <masao.fujii@xxxxxxxxx>
So, that means that the only ways to stop streaming replication are to stop the slave server, to disable access to the master via the pg_hba.conf file (requiring the master configs be reloaded) or to set the trigger file on the slave to tell it to stop replicating the master.
And if the master/slave are set to synchronous streaming replication, your options are more limited, since the master has to know to stop waiting for the synchronous slave to respond.
Once the slave has gone out of asynchronous replication mode, wuld it be possible to resume asynchronous replication by stopping the slave server, removing the trigger file, and restarting it in asynchronous streaming replication mode? This would, at a minimum, depend on how many updates have occurred on the master during the time streaming replication was disabled and having all the WAL files available, right?
--
Mike Nolan
From: Michael Nolan <htfoot@xxxxxxxxx>
Date: Tue, May 29, 2012 at 1:37 PM
Subject: Re: Disable Streaming Replication without restarting either master or slave
To: Fujii Masao <masao.fujii@xxxxxxxxx>
> Are per-chance looking for pg_xlog_replay_pause() andThose can pause and resume WAL replay in the standby, but not streaming
> pg_xlog_replay_resume() ?
replication. Even while WAL replay is being paused, WAL can be streamed
from the master to the standby.
Regards,
--
Fujii Masao
So, that means that the only ways to stop streaming replication are to stop the slave server, to disable access to the master via the pg_hba.conf file (requiring the master configs be reloaded) or to set the trigger file on the slave to tell it to stop replicating the master.
And if the master/slave are set to synchronous streaming replication, your options are more limited, since the master has to know to stop waiting for the synchronous slave to respond.
Once the slave has gone out of asynchronous replication mode, wuld it be possible to resume asynchronous replication by stopping the slave server, removing the trigger file, and restarting it in asynchronous streaming replication mode? This would, at a minimum, depend on how many updates have occurred on the master during the time streaming replication was disabled and having all the WAL files available, right?
--
Mike Nolan
