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

[Anssi Kanninen]

Hi,

Thank you for the answer, Pierre! I'll try that also.

Is there any downside on not dropping the replication slots at all? If I 
create them once on the primary and let them be there until other node is 
promoted as primary?

Cheers,
   - Anssi

On Fri, 5 Jun 2020, Pierre Timmermans wrote:

> Hi
> 
> 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
> 
> 
> Pierre
> 
> 
> 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
> Japanese:http://www.sraoss.co.jp
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general
> 
>

-- 
anssi at iki.fi