[pgpool-general: 7073] Re: Rebooting the cluster?

Pierre Timmermans ptim007 at yahoo.com
Fri Jun 5 14:52:53 JST 2020

Another solution is to change the startup script of pgpool so that the start of pgpool is delayed until all the databases are up. So loop trying to connect to each backend database until success, with a max timeout


    On Friday, June 5, 2020, 1:57:40 AM GMT+2, Tatsuo Ishii <ishii at sraoss.co.jp> wrote:  
 >> There's a parameter called "auto_failback" which automatically
>> attaches a PostgreSQL standby node if it's safe. auto_failback is
>> available in 4.1 or later.
> Thank you again for quick answer!
> That works but requires some changes to the example failover.sh
> -script. The replication slot is dropped if standby node goes down. So
> to get auto_failback working, the replication slot must be recreated
> or not to be dropped at all.

True. Peng, what do you think?

Best regards,
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
pgpool-general mailing list
pgpool-general at pgpool.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20200605/86e3d1e9/attachment.html>

More information about the pgpool-general mailing list