public inbox for [email protected]
help / color / mirror / Atom feedPgpool-II 4.7.0 released.
17+ messages / 3 participants
[nested] [flat]
* Pgpool-II 4.7.0 released.
@ 2025-12-23 04:38 Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Koshino Taiki @ 2025-12-23 04:38 UTC (permalink / raw)
To: [email protected] <[email protected]>
Pgpool Global Development Group is pleased to announce the availability of Pgpool-II 4.7.0.
This is the first stable release of Pgpool-II 4.7.x.
V4.7 contains new features and enhancements, including:
* Retire Slony mode.
* Rename logdir parameter to work_dir.
* Add support for frontend/backend protocol version 3.2.
* Enhance security for watchdog and heartbeat receiver.
* Add new fields to pcp_proc_info and show pool_pools to display client information, and add pgpool_adm_pcp_proc_info extension function.
* Make online recovery database configurable.
* Import PostgreSQL 18's SQL parser.
You can download it from:
https://www.pgpool.net/mediawiki/index.php/Downloads
Please see the release notes at:
https://www.pgpool.net/docs/47/en/html/release-4-7-0.html
Taiki Koshino<[email protected]>
SRA OSS K.K.
TEL: 03-5979-2701 FAX: 03-5979-2702
URL: https://www.sraoss.co.jp/
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
@ 2025-12-29 14:11 ` Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Emond Papegaaij @ 2025-12-29 14:11 UTC (permalink / raw)
To: [email protected] <[email protected]>
Hi all,
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:05: pid 8: LOG: setting the local watchdog node name
to "172.29.30.1:5432 Linux 9ade096c54fb"
2025-12-29 10:11:05: pid 8: LOG: watchdog cluster is configured with
1 remote nodes
2025-12-29 10:11:05: pid 8: LOG: watchdog remote node:0 on 172.29.30.2:9009
2025-12-29 10:11:05: pid 8: LOG: interface monitoring is disabled in watchdog
2025-12-29 10:11:05: pid 8: LOG: setting up watchdog receive socket
for 172.29.30.1:9009
2025-12-29 10:11:05: pid 8: LOG: failed to create watchdog receive
socket. retrying...
2025-12-29 10:11:05: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
with reason: "Address not available"
2025-12-29 10:11:06: pid 8: LOG: failed to create watchdog receive
socket. retrying...
2025-12-29 10:11:06: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
with reason: "Address not available"
2025-12-29 10:11:07: pid 8: LOG: failed to create watchdog receive
socket. retrying...
2025-12-29 10:11:07: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
with reason: "Address not available"
2025-12-29 10:11:08: pid 8: LOG: failed to create watchdog receive
socket. retrying...
2025-12-29 10:11:08: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
with reason: "Address not available"
2025-12-29 10:11:09: pid 8: LOG: failed to create watchdog receive
socket. retrying...
2025-12-29 10:11:09: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
with reason: "Address not available"
2025-12-29 10:11:10: pid 8: LOG: failed to create watchdog receive socket
2025-12-29 10:11:10: pid 8: DETAIL: bind on 172.29.30.1:9009 failed
2025-12-29 10:11:10: pid 8: FATAL: failed to create any of watchdog
receive sockets
2025-12-29 10:11:10: pid 1: DEBUG: reaper handler
2025-12-29 10:11:10: pid 1: DEBUG: watchdog child process with pid: 8
exit with FATAL ERROR. pgpool-II will be shutdown
2025-12-29 10:11:10: pid 1: DEBUG: watchdog child process with pid: 8
exits with status 768
2025-12-29 10:11:10: pid 1: FATAL: watchdog child process exit with
fatal error. exiting pgpool-II
2025-12-29 10:11:10: pid 1: LOG: shutting down
The configuration for the watchdog and heartbeats hosts and ports is:
hostname0 = '172.29.30.1'
wd_port0 = 9009
pgpool_port0 = 5432
heartbeat_hostname0 = '172.29.30.1'
heartbeat_port0 = 9694
hostname1 = '172.29.30.2'
wd_port1 = 9009
pgpool_port1 = 5432
heartbeat_hostname1 = '172.29.30.2'
heartbeat_port1 = 9694
hostname2 = '172.29.30.3'
wd_port2 = 9009
pgpool_port2 = 5432
heartbeat_hostname2 = '172.29.30.3'
heartbeat_port2 = 9694
Is there any way to revert this behavior to the old situation, where
pgpool would bind on all IP addresses? Inside a docker container, this
is fine.
Best regards,
Emond
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
@ 2025-12-31 00:23 ` Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Tatsuo Ishii @ 2025-12-31 00:23 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
> Hi all,
>
> 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:05: pid 8: LOG: setting the local watchdog node name
> to "172.29.30.1:5432 Linux 9ade096c54fb"
> 2025-12-29 10:11:05: pid 8: LOG: watchdog cluster is configured with
> 1 remote nodes
> 2025-12-29 10:11:05: pid 8: LOG: watchdog remote node:0 on 172.29.30.2:9009
> 2025-12-29 10:11:05: pid 8: LOG: interface monitoring is disabled in watchdog
> 2025-12-29 10:11:05: pid 8: LOG: setting up watchdog receive socket
> for 172.29.30.1:9009
> 2025-12-29 10:11:05: pid 8: LOG: failed to create watchdog receive
> socket. retrying...
> 2025-12-29 10:11:05: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
> with reason: "Address not available"
> 2025-12-29 10:11:06: pid 8: LOG: failed to create watchdog receive
> socket. retrying...
> 2025-12-29 10:11:06: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
> with reason: "Address not available"
> 2025-12-29 10:11:07: pid 8: LOG: failed to create watchdog receive
> socket. retrying...
> 2025-12-29 10:11:07: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
> with reason: "Address not available"
> 2025-12-29 10:11:08: pid 8: LOG: failed to create watchdog receive
> socket. retrying...
> 2025-12-29 10:11:08: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
> with reason: "Address not available"
> 2025-12-29 10:11:09: pid 8: LOG: failed to create watchdog receive
> socket. retrying...
> 2025-12-29 10:11:09: pid 8: DETAIL: bind on "172.29.30.1:9009" failed
> with reason: "Address not available"
> 2025-12-29 10:11:10: pid 8: LOG: failed to create watchdog receive socket
> 2025-12-29 10:11:10: pid 8: DETAIL: bind on 172.29.30.1:9009 failed
> 2025-12-29 10:11:10: pid 8: FATAL: failed to create any of watchdog
> receive sockets
> 2025-12-29 10:11:10: pid 1: DEBUG: reaper handler
> 2025-12-29 10:11:10: pid 1: DEBUG: watchdog child process with pid: 8
> exit with FATAL ERROR. pgpool-II will be shutdown
> 2025-12-29 10:11:10: pid 1: DEBUG: watchdog child process with pid: 8
> exits with status 768
> 2025-12-29 10:11:10: pid 1: FATAL: watchdog child process exit with
> fatal error. exiting pgpool-II
> 2025-12-29 10:11:10: pid 1: LOG: shutting down
>
> The configuration for the watchdog and heartbeats hosts and ports is:
> hostname0 = '172.29.30.1'
> wd_port0 = 9009
> pgpool_port0 = 5432
> heartbeat_hostname0 = '172.29.30.1'
> heartbeat_port0 = 9694
>
> hostname1 = '172.29.30.2'
> wd_port1 = 9009
> pgpool_port1 = 5432
> heartbeat_hostname1 = '172.29.30.2'
> heartbeat_port1 = 9694
>
> hostname2 = '172.29.30.3'
> wd_port2 = 9009
> pgpool_port2 = 5432
> heartbeat_hostname2 = '172.29.30.3'
> heartbeat_port2 = 9694
>
> Is there any way to revert this behavior to the old situation, where
> pgpool would bind on all IP addresses? Inside a docker container, this
> is fine.
Sorry for the inconvenience.
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 ...").
Since most pgpool developers are off for New Year's holiday, I will
discuss them next week.
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
@ 2025-12-31 06:57 ` Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Emond Papegaaij @ 2025-12-31 06:57 UTC (permalink / raw)
To: Tatsuo Ishii <[email protected]>; +Cc: [email protected]
> > 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
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
@ 2025-12-31 07:57 ` Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Tatsuo Ishii @ 2025-12-31 07:57 UTC (permalink / raw)
To: [email protected]; +Cc: [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.
>
> 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
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
@ 2026-01-20 07:43 ` Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Emond Papegaaij @ 2026-01-20 07:43 UTC (permalink / raw)
To: Tatsuo Ishii <[email protected]>; +Cc: [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
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
@ 2026-01-22 00:30 ` Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Tatsuo Ishii @ 2026-01-22 00:30 UTC (permalink / raw)
To: [email protected]; +Cc: [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?
I and Pengbo are discussing this off list. We are leaning towards
adding "listen_addresses" like parameters as other parameters prefers
"listen" over "bind" ("listen_addresses" and "pcp_listen_addresses").
We are thinking to add:
wd_listen_addresses0=''
heartbeat_listen_addresses0=''
:
:
because watchdog and hearbeat needs separate listen addresses
parameter. So if we would add these parameters, users will need to
configure number_of_watchdog_nodes * 2 parameters, which will be a
pain.
One way to mitigate this is, to consider default values for these
parameters if they are not specified. There are two candidate for the
default value.
(1) "*"
This is similar to the pre-4.7 behavior, but less secure.
(2) same as hostname0 (for wd_listen_addresses0) and
heartbeat_hostname0 (for heartbeat_hostname0).
This is current 4.7 behavior and more secure but does not work for
your environment.
What do you think?
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
@ 2026-01-22 10:05 ` Emond Papegaaij <[email protected]>
2026-01-23 04:35 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Emond Papegaaij @ 2026-01-22 10:05 UTC (permalink / raw)
To: Tatsuo Ishii <[email protected]>; +Cc: [email protected]
Op do 22 jan 2026 om 01:30 schreef Tatsuo Ishii <[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?
>
> I and Pengbo are discussing this off list. We are leaning towards
> adding "listen_addresses" like parameters as other parameters prefers
> "listen" over "bind" ("listen_addresses" and "pcp_listen_addresses").
That makes sense indeed.
> We are thinking to add:
> wd_listen_addresses0=''
> heartbeat_listen_addresses0=''
> :
> :
>
> because watchdog and hearbeat needs separate listen addresses
> parameter. So if we would add these parameters, users will need to
> configure number_of_watchdog_nodes * 2 parameters, which will be a
> pain.
I would expect to only have to configure 2 listen_addresses, because a
single instance only listens once per service (watchdog and
heartbeat). Is there a reason to have to configure the listen
addresses for all nodes on every node? Why does node 0 need to know
the listen address of nodes 1 and 2?
Isn't it possible to add the configuration like this:
wd_listen_address = '*'
wd_port = 9009
wd_heartbeat_listen_address = '*'
wd_heartbeat_port = 9694
I think it's also better to not assume the listen address and port are
identical to the address and port on which to connect. For example,
specific TCP forwarding rules might redirect traffic to entirely
different addresses and ports. So node 0 might listen at
192.168.3.50:10000, but TCP forwarding rules might require node 1 to
connect to 10.0.3.50:9009 to connect to node 0.
> One way to mitigate this is, to consider default values for these
> parameters if they are not specified. There are two candidate for the
> default value.
>
> (1) "*"
>
> This is similar to the pre-4.7 behavior, but less secure.
>
> (2) same as hostname0 (for wd_listen_addresses0) and
> heartbeat_hostname0 (for heartbeat_hostname0).
>
> This is current 4.7 behavior and more secure but does not work for
> your environment.
>
> What do you think?
I think, whatever implementation for the new parameters is chosen, the
default behavior or 4.7 should not change. So I'd go for option 2. I
don't mind having to change the configuration to get 4.7 working for
us, but I wouldn't expect a new version to be less secure by default
than the previous version was.
Best regards,
Emond
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
@ 2026-01-23 04:35 ` Tatsuo Ishii <[email protected]>
2026-01-23 07:25 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Tatsuo Ishii @ 2026-01-23 04:35 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
>> We are thinking to add:
>> wd_listen_addresses0=''
>> heartbeat_listen_addresses0=''
>> :
>> :
>>
>> because watchdog and hearbeat needs separate listen addresses
>> parameter. So if we would add these parameters, users will need to
>> configure number_of_watchdog_nodes * 2 parameters, which will be a
>> pain.
>
> I would expect to only have to configure 2 listen_addresses, because a
> single instance only listens once per service (watchdog and
> heartbeat). Is there a reason to have to configure the listen
> addresses for all nodes on every node? Why does node 0 need to know
> the listen address of nodes 1 and 2?
>
> Isn't it possible to add the configuration like this:
> wd_listen_address = '*'
> wd_port = 9009
> wd_heartbeat_listen_address = '*'
> wd_heartbeat_port = 9694
Ok, that makes sense.
wd_listen_addresses (consistent with listen_addresses)
wd_listen_port (wd_port already exists)
wd_heartbeat_listen_addresses (consistent with listen_addresses)
wd_heartbeat_listen_port (adding "listen" looks more consistent with other params)
> I think it's also better to not assume the listen address and port are
> identical to the address and port on which to connect. For example,
> specific TCP forwarding rules might redirect traffic to entirely
> different addresses and ports. So node 0 might listen at
> 192.168.3.50:10000, but TCP forwarding rules might require node 1 to
> connect to 10.0.3.50:9009 to connect to node 0.
Ok, so we will have following 4 new params?
wd_listen_addresses
wd_listen_port
wd_heartbeat_listen_addresses
wd_heartbeat_listen_port
>> One way to mitigate this is, to consider default values for these
>> parameters if they are not specified. There are two candidate for the
>> default value.
>>
>> (1) "*"
>>
>> This is similar to the pre-4.7 behavior, but less secure.
>>
>> (2) same as hostname0 (for wd_listen_addresses0) and
>> heartbeat_hostname0 (for heartbeat_hostname0).
>>
>> This is current 4.7 behavior and more secure but does not work for
>> your environment.
>>
>> What do you think?
>
> I think, whatever implementation for the new parameters is chosen, the
> default behavior or 4.7 should not change. So I'd go for option 2. I
> don't mind having to change the configuration to get 4.7 working for
> us, but I wouldn't expect a new version to be less secure by default
> than the previous version was.
Agreed.
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 04:35 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
@ 2026-01-23 07:25 ` Tatsuo Ishii <[email protected]>
2026-01-23 09:02 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Tatsuo Ishii @ 2026-01-23 07:25 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
> Ok, so we will have following 4 new params?
>
> wd_listen_addresses
> wd_listen_port
> wd_heartbeat_listen_addresses
> wd_heartbeat_listen_port
After thinking more, I feel like it would be overkill to allow to
specify multiple IPs for wd_listen_addresses and
wd_heartbeat_listen_addresses.
If so, we can decide to allow only 1 IP for each parameter and change
the names to:
wd_listen_address
wd_heartbeat_listen_address
What do you think?
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 04:35 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 07:25 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
@ 2026-01-23 09:02 ` Emond Papegaaij <[email protected]>
2026-01-23 10:01 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Emond Papegaaij @ 2026-01-23 09:02 UTC (permalink / raw)
To: Tatsuo Ishii <[email protected]>; +Cc: [email protected]
Op vr 23 jan 2026 om 08:25 schreef Tatsuo Ishii <[email protected]>:
>
> > Ok, so we will have following 4 new params?
> >
> > wd_listen_addresses
> > wd_listen_port
> > wd_heartbeat_listen_addresses
> > wd_heartbeat_listen_port
>
> After thinking more, I feel like it would be overkill to allow to
> specify multiple IPs for wd_listen_addresses and
> wd_heartbeat_listen_addresses.
>
> If so, we can decide to allow only 1 IP for each parameter and change
> the names to:
>
> wd_listen_address
> wd_heartbeat_listen_address
>
> What do you think?
Yes, that makes sense to me. I don't see any reason to have multiple
addresses for those. If you do allow multiple addresses, that would
only be for consistency with the other options, like listen_addresses
and pcp_listen_addresses. We are going to use '*' anyway, because in a
docker container that works fine.
For some reason, our configuration file already contains a
wd_heartbeat_port, which I can't find in the manual. But it even
contains a comment stating that a change requires a restart, so it
must have come from somewhere:
wd_heartbeat_port = 9694
# Port number for receiving heartbeat signal
# (change requires restart)
Best regards,
Emond
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 04:35 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 07:25 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 09:02 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
@ 2026-01-23 10:01 ` Tatsuo Ishii <[email protected]>
2026-01-23 10:42 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Tatsuo Ishii @ 2026-01-23 10:01 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
>> After thinking more, I feel like it would be overkill to allow to
>> specify multiple IPs for wd_listen_addresses and
>> wd_heartbeat_listen_addresses.
>>
>> If so, we can decide to allow only 1 IP for each parameter and change
>> the names to:
>>
>> wd_listen_address
>> wd_heartbeat_listen_address
>>
>> What do you think?
>
> Yes, that makes sense to me. I don't see any reason to have multiple
> addresses for those. If you do allow multiple addresses, that would
> only be for consistency with the other options, like listen_addresses
> and pcp_listen_addresses. We are going to use '*' anyway, because in a
> docker container that works fine.
Ok.
> For some reason, our configuration file already contains a
> wd_heartbeat_port, which I can't find in the manual. But it even
> contains a comment stating that a change requires a restart, so it
> must have come from somewhere:
>
> wd_heartbeat_port = 9694
> # Port number for receiving heartbeat signal
> # (change requires restart)
wd_heartbeat_port was once in older versions of pgpool.conf,
e.g. v3.3.
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 04:35 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 07:25 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 09:02 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 10:01 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
@ 2026-01-23 10:42 ` Emond Papegaaij <[email protected]>
2026-01-23 22:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Emond Papegaaij @ 2026-01-23 10:42 UTC (permalink / raw)
To: Tatsuo Ishii <[email protected]>; +Cc: [email protected]
> > For some reason, our configuration file already contains a
> > wd_heartbeat_port, which I can't find in the manual. But it even
> > contains a comment stating that a change requires a restart, so it
> > must have come from somewhere:
> >
> > wd_heartbeat_port = 9694
> > # Port number for receiving heartbeat signal
> > # (change requires restart)
>
> wd_heartbeat_port was once in older versions of pgpool.conf,
> e.g. v3.3.
Ah, that explains it. Perhaps we should review our configuration file
against the manual to check if more options have changed over the
years. We've been using pgpool for quite some time now. Thanks for the
explanation.
Best regards,
Emond
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 04:35 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 07:25 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 09:02 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 10:01 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 10:42 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
@ 2026-01-23 22:57 ` Tatsuo Ishii <[email protected]>
2026-01-26 10:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Tatsuo Ishii @ 2026-01-23 22:57 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
>> wd_heartbeat_port was once in older versions of pgpool.conf,
>> e.g. v3.3.
>
> Ah, that explains it. Perhaps we should review our configuration file
> against the manual to check if more options have changed over the
> years. We've been using pgpool for quite some time now. Thanks for the
> explanation.
The removal happend in 4.2.0 and it was explained in the release note.
https://www.pgpool.net/docs/42/en/html/release-4-2-0.html
See the section "A.25.2. Migration to Version 4.2":
> Watchdog parameters below are deprecated.
>
> - wd_hostname
> - wd_port
> - wd_heartbeat_port <--- here
> - heartbeat_device
> - heartbeat_destination0
> - heartbeat_destination_port0
> - heartbeat_destination1
> - heartbeat_destination_port1
> - other_pgpool_hostname0
> - other_pgpool_port0
> - other_wd_port0
> - other_pgpool_hostname1
> - other_pgpool_port1
> - other_wd_port1
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 04:35 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 07:25 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 09:02 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 10:01 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 10:42 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 22:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
@ 2026-01-26 10:57 ` Emond Papegaaij <[email protected]>
2026-02-25 05:14 ` Re: Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Emond Papegaaij @ 2026-01-26 10:57 UTC (permalink / raw)
To: Tatsuo Ishii <[email protected]>; +Cc: [email protected]
> The removal happend in 4.2.0 and it was explained in the release note.
> https://www.pgpool.net/docs/42/en/html/release-4-2-0.html
>
> See the section "A.25.2. Migration to Version 4.2":
>
> > Watchdog parameters below are deprecated.
> >
> > - wd_hostname
> > - wd_port
> > - wd_heartbeat_port <--- here
> > - heartbeat_device
> > - heartbeat_destination0
> > - heartbeat_destination_port0
> > - heartbeat_destination1
> > - heartbeat_destination_port1
> > - other_pgpool_hostname0
> > - other_pgpool_port0
> > - other_wd_port0
> > - other_pgpool_hostname1
> > - other_pgpool_port1
> > - other_wd_port1
Thanks. I must have missed wd_heartbeat_port during that upgrade step.
All others were already removed.
Best regards,
Emond
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 04:35 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 07:25 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 09:02 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 10:01 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 10:42 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 22:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-26 10:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
@ 2026-02-25 05:14 ` Koshino Taiki <[email protected]>
2026-02-25 19:55 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
0 siblings, 1 reply; 17+ messages in thread
From: Koshino Taiki @ 2026-02-25 05:14 UTC (permalink / raw)
To: Emond Papegaaij <[email protected]>; Tatsuo Ishii <[email protected]>; +Cc: [email protected] <[email protected]>
Hi,
We have added the parameters wd_listen_port and wd_listen_address to allow specifying the address and port on which watchdog listens,
as well as wd_heartbeat_listen_addresses and wd_heartbeat_listen_port to configure the addresses and port on which heartbeat receiver process listens.
These parameters will be available starting from the next minor release.
https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=7bfc5e9898e5999fc4330c5479b4f52294b699b5
Best regards,
Taiki Koshino<[email protected]>
SRA OSS K.K.
TEL: 03-5979-2701 FAX: 03-5979-2702
URL: https://www.sraoss.co.jp/
________________________________
差出人: Emond Papegaaij <[email protected]>
送信日時: 2026年1月26日 19:57
宛先: Tatsuo Ishii <[email protected]>
CC: [email protected] <[email protected]>
件名: Re: Pgpool-II 4.7.0 released.
> The removal happend in 4.2.0 and it was explained in the release note.
> https://www.pgpool.net/docs/42/en/html/release-4-2-0.html
>
> See the section "A.25.2. Migration to Version 4.2":
>
> > Watchdog parameters below are deprecated.
> >
> > - wd_hostname
> > - wd_port
> > - wd_heartbeat_port <--- here
> > - heartbeat_device
> > - heartbeat_destination0
> > - heartbeat_destination_port0
> > - heartbeat_destination1
> > - heartbeat_destination_port1
> > - other_pgpool_hostname0
> > - other_pgpool_port0
> > - other_wd_port0
> > - other_pgpool_hostname1
> > - other_pgpool_port1
> > - other_wd_port1
Thanks. I must have missed wd_heartbeat_port during that upgrade step.
All others were already removed.
Best regards,
Emond
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: Pgpool-II 4.7.0 released.
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 04:35 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 07:25 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 09:02 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 10:01 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-23 10:42 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-01-23 22:57 ` Re: Pgpool-II 4.7.0 released. Tatsuo Ishii <[email protected]>
2026-01-26 10:57 ` Re: Pgpool-II 4.7.0 released. Emond Papegaaij <[email protected]>
2026-02-25 05:14 ` Re: Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
@ 2026-02-25 19:55 ` Emond Papegaaij <[email protected]>
0 siblings, 0 replies; 17+ messages in thread
From: Emond Papegaaij @ 2026-02-25 19:55 UTC (permalink / raw)
To: [email protected]
Hi,
Thanks for taking care of this. We will give it a try when the next release
is out.
Best regards,
Emond Papegaaij
Op wo 25 feb 2026, 06:14 schreef Koshino Taiki <[email protected]>:
> Hi,
>
> We have added the parameters wd_listen_port and wd_listen_address to allow
> specifying the address and port on which watchdog listens,
> as well as wd_heartbeat_listen_addresses and wd_heartbeat_listen_port to
> configure the addresses and port on which heartbeat receiver process
> listens.
>
> These parameters will be available starting from the next minor release.
>
> https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=7bfc5e9898e5999fc4330c5479b4f52294b699b5
>
> Best regards,
>
> Taiki Koshino<[email protected]>
> SRA OSS K.K.
> TEL: 03-5979-2701 FAX: 03-5979-2702
> URL: https://www.sraoss.co.jp/
>
> ------------------------------
> *差出人:* Emond Papegaaij <[email protected]>
> *送信日時:* 2026年1月26日 19:57
> *宛先:* Tatsuo Ishii <[email protected]>
> *CC:* [email protected] <
> [email protected]>
> *件名:* Re: Pgpool-II 4.7.0 released.
>
> > The removal happend in 4.2.0 and it was explained in the release note.
> > https://www.pgpool.net/docs/42/en/html/release-4-2-0.html
> >
> > See the section "A.25.2. Migration to Version 4.2":
> >
> > > Watchdog parameters below are deprecated.
> > >
> > > - wd_hostname
> > > - wd_port
> > > - wd_heartbeat_port <--- here
> > > - heartbeat_device
> > > - heartbeat_destination0
> > > - heartbeat_destination_port0
> > > - heartbeat_destination1
> > > - heartbeat_destination_port1
> > > - other_pgpool_hostname0
> > > - other_pgpool_port0
> > > - other_wd_port0
> > > - other_pgpool_hostname1
> > > - other_pgpool_port1
> > > - other_wd_port1
>
> Thanks. I must have missed wd_heartbeat_port during that upgrade step.
> All others were already removed.
>
> Best regards,
> Emond
>
>
>
^ permalink raw reply [nested|flat] 17+ messages in thread
end of thread, other threads:[~2026-02-25 19:55 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-12-23 04:38 Pgpool-II 4.7.0 released. Koshino Taiki <[email protected]>
2025-12-29 14:11 ` Emond Papegaaij <[email protected]>
2025-12-31 00:23 ` Tatsuo Ishii <[email protected]>
2025-12-31 06:57 ` Emond Papegaaij <[email protected]>
2025-12-31 07:57 ` Tatsuo Ishii <[email protected]>
2026-01-20 07:43 ` Emond Papegaaij <[email protected]>
2026-01-22 00:30 ` Tatsuo Ishii <[email protected]>
2026-01-22 10:05 ` Emond Papegaaij <[email protected]>
2026-01-23 04:35 ` Tatsuo Ishii <[email protected]>
2026-01-23 07:25 ` Tatsuo Ishii <[email protected]>
2026-01-23 09:02 ` Emond Papegaaij <[email protected]>
2026-01-23 10:01 ` Tatsuo Ishii <[email protected]>
2026-01-23 10:42 ` Emond Papegaaij <[email protected]>
2026-01-23 22:57 ` Tatsuo Ishii <[email protected]>
2026-01-26 10:57 ` Emond Papegaaij <[email protected]>
2026-02-25 05:14 ` Koshino Taiki <[email protected]>
2026-02-25 19:55 ` Emond Papegaaij <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox