Re: Pgpool-II 4.7.0 released.

From: Emond Papegaaij <emond(dot)papegaaij(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgpool-general(at)lists(dot)postgresql(dot)org
Subject: Re: Pgpool-II 4.7.0 released.
Date: 2026-01-20 07:43:39
Message-ID: CAGXsc+au8Wzjsuk1z-mqPFLfpkjQZSPneLLVbnkUs5rAMXNF=A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgpool-general

Op wo 31 dec 2025 om 08:57 schreef Tatsuo Ishii <ishii(at)postgresql(dot)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

In response to

Responses

Browse pgpool-general by date

  From Date Subject
Next Message Tatsuo Ishii 2026-01-22 00:30:03 Re: Pgpool-II 4.7.0 released.
Previous Message Bo Peng 2026-01-15 11:02:42 Re: pgpool2_on_k8s repo status