search

pgpool / pgpool2

This is the official mirror of git://git.postgresql.org/git/pgpool2.git. Note that this is just a *mirror* - we don't work with pull requests on github. Please subscribe to pgpool-hackers mailing list from our website and submit your patch to this mailing list.
https://www.pgpool.net
Other
305 stars 87 forks source link

IPv6 is not supported by Watch Dog heartbeat #21

Open OneMoreSec opened 5 years ago

OneMoreSec commented 5 years ago

I am using Pgpool II 3.7.3. Property "heartbeat_destination" is set as an IPv6, and it produces an error that is "failed to send watchdog heartbeat, gethostbyname() failed". Does this property only support IPv4?

pgpool-tmp commented 5 years ago

Currently Pgpool-II supports IPv6 only for PostgreSQL backend server and bind address of Pgpool-II itself. Other than this, including watchdg hearbeat, do not support IPv6.

cbid71 commented 1 month ago

Hello, Is there some news about this point ?

I tried for the last days to make it work under pgpool 4.4.4 , maybe I should habe RTFM earlier, but the code was blocking on this point :

2024-05-22 13:05:09.204: heart_beat_sender pid 63087: ERROR:  failed to send watchdog heartbeat, gethostbyname() failed
2024-05-22 13:05:09.204: heart_beat_sender pid 63087: DETAIL:  gethostbyname on "myserver" failed with reason: "No address associated with name"

I was reproducing the problem under python, maybe was it related to this problem ?

https://docs.python.org/3/library/socket.html#socket.gethostbyname

[gethostbyname()](https://docs.python.org/3/library/socket.html#socket.gethostbyname) does not support IPv6 name resolution, and [getaddrinfo()](https://docs.python.org/3/library/socket.html#socket.getaddrinfo) should be used instead for IPv4/v6 dual stack support.
rnalrd commented 2 weeks ago

+1 in having full dual-stack support, from frontend to backend