public inbox for [email protected]
help / color / mirror / Atom feedFrom: Emond Papegaaij <[email protected]>
To: Tatsuo Ishii <[email protected]>
Cc: [email protected]
Subject: Re: Pgpool-II 4.7.0 released.
Date: Tue, 20 Jan 2026 08:43:39 +0100
Message-ID: <CAGXsc+au8Wzjsuk1z-mqPFLfpkjQZSPneLLVbnkUs5rAMXNF=A@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAGXsc+Yo7zOYmqLwcf_uoFUFn65jpySUU-QAseKn7rzr_zAmLA@mail.gmail.com>
<[email protected]>
<CAGXsc+ZM=aE=ibSDintubM8Ni8kfeaXK963Xca05j-SBYLPhhA@mail.gmail.com>
<[email protected]>
Op wo 31 dec 2025 om 08:57 schreef Tatsuo Ishii <[email protected]>:
> >> Unfortunately it's not possible to bind on all IP addresses for pgpool
> >> by tweaking hostnameN. You could specify it to '*' so that it binds on
> >> all IP addresses, but this will cause a different problem:
> >> communicating to other watchdog is refused. This is because each
> >> watchdog node name is created from hostnameN. If hostnameN is '*', the
> >> node name will be something like "*:5432 Linux..." which is different
> >> from what other watchdog nodes expect (they expect something like
> >> '172.29.30.1:5432 ...").
> >
> > I already suspected this. The same goes for using the actual docker
> > container ip, which is 172.29.29.107 on all 3 nodes. I think the best
> > solution would be to introduce a bind_address configuration parameter,
> > which defaults to hostnameN, but can be overridden. I guess the same
> > thing goes for heartbeat_hostnameN.
>
> Yeah, I thought the same. I will discuss with other developers next
> year.
>
> >> Since most pgpool developers are off for New Year's holiday, I will
> >> discuss them next week.
Do you have an update on this already?
Best regards,
Emond
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Pgpool-II 4.7.0 released.
In-Reply-To: <CAGXsc+au8Wzjsuk1z-mqPFLfpkjQZSPneLLVbnkUs5rAMXNF=A@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox