Re: Pgpool-II 4.7.0 released.

> > We are trying to upgrade our application to use Pgpool-II 4.7.0, but
> > the change for 'Enhance security for watchdog and heartbeat receiver.'
> > is causing issues for us. We run Pgpool in a docker container and
> > expose some of its ports to specific IP-addresses on the hosts:
> > 172.29.30.1, 172.29.30.2 and 172.29.30.3 for the 3 hosts. However,
> > from the perspective of docker container in which Pgpool is running,
> > there's only the IP assigned to the container by docker. With 4.7.0,
> > Pgpool tries to bind the wd_port to its external IP address, which is
> > not possible from inside the container, resulting in the following
> > errors:
> >
> > 2025-12-29 10:11:07: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
> > with reason: "Address not available"
>
> Sorry for the inconvenience.

No problem. These things happen.

> 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.

> Since most pgpool developers are off for New Year's holiday, I will
> discuss them next week.

No need to hurry. 4.6.5 is working fine for us at the moment. I wish
you a happy new year in advance.

Best regards,
Emond