MIME-Version: 1.0
References: 
 <CAGXsc+Yo7zOYmqLwcf_uoFUFn65jpySUU-QAseKn7rzr_zAmLA@mail.gmail.com>
 <20251231.092344.1606071176472398412.ishii@postgresql.org>
 <CAGXsc+ZM=aE=ibSDintubM8Ni8kfeaXK963Xca05j-SBYLPhhA@mail.gmail.com>
 <20251231.165714.1023017053914495270.ishii@postgresql.org>
In-Reply-To: <20251231.165714.1023017053914495270.ishii@postgresql.org>
From: Emond Papegaaij <emond.papegaaij@gmail.com>
Date: Tue, 20 Jan 2026 08:43:39 +0100
Message-ID: 
 <CAGXsc+au8Wzjsuk1z-mqPFLfpkjQZSPneLLVbnkUs5rAMXNF=A@mail.gmail.com>
Subject: Re: Pgpool-II 4.7.0 released.
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: pgpool-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAGXsc%2Bau8Wzjsuk1z-mqPFLfpkjQZSPneLLVbnkUs5rAMXNF%3DA%40mail.gmail.com>
Precedence: bulk

Op wo 31 dec 2025 om 08:57 schreef Tatsuo Ishii <ishii@postgresql.org>:
> >> 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