[pgpool-general: 5375] Re: [pgpool] Streaming Replication - Identify Slave Node Status

Lazaro Garcia lazaro3487 at gmail.com
Thu Mar 16 22:06:38 JST 2017

When slave goes down, pgpool detects that and triggers a failover, then the master remains active and the slave are marked as down state. On the failover_command of pgpool, you could execute a command that drop the slave from the master synchronous_standby_names and reload the configuration on the master. By this way new transactions can be executed on the master without checking the state of the slave because synchronous replication has been disabled.


If you recover the slave you can attach this server to master again an activate the synchronous replication.





De: pgpool-general-bounces at pgpool.net [mailto:pgpool-general-bounces at pgpool.net] En nombre de Anushka Weerakkodyge
Enviado el: miércoles, 15 de marzo de 2017 05:37 p. m.
Para: pgpool-general at pgpool.net
Asunto: [pgpool-general: 5370] [pgpool] Streaming Replication - Identify Slave Node Status


Hi all,


I have a synchronous streaming replication environment which is implemented using inbuilt replication mechanism in postgresql. There is a requirement that I need to fail the data modification transactions on master node if the slave node is down. (ie: transactions should commit when only both servers are up and running) 


Please let me know whether there is a way to identify slave node status and fail the transaction using pgpool ? 




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170316/1e0010c6/attachment.html>

More information about the pgpool-general mailing list