Date: Wed, 31 Dec 2025 16:57:14 +0900 (JST)
Message-Id: <20251231.165714.1023017053914495270.ishii@postgresql.org>
To: emond.papegaaij@gmail.com
Cc: pgpool-general@lists.postgresql.org
Subject: Re: Pgpool-II 4.7.0 released.
From: Tatsuo Ishii <ishii@postgresql.org>
In-Reply-To: 
 <CAGXsc+ZM=aE=ibSDintubM8Ni8kfeaXK963Xca05j-SBYLPhhA@mail.gmail.com>
References: 
 <CAGXsc+Yo7zOYmqLwcf_uoFUFn65jpySUU-QAseKn7rzr_zAmLA@mail.gmail.com>
	<20251231.092344.1606071176472398412.ishii@postgresql.org>
	<CAGXsc+ZM=aE=ibSDintubM8Ni8kfeaXK963Xca05j-SBYLPhhA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/20251231.165714.1023017053914495270.ishii%40postgresql.org>
Precedence: bulk

>> 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.
> 
> No need to hurry. 4.6.5 is working fine for us at the moment. I wish
> you a happy new year in advance.

Thanks.
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp