Open OneMoreSec opened 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.
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 have 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.
+1 in having full dual-stack support, from frontend to backend
I have updated our TODO item for this: https://pgpool.net/mediawiki/index.php/TODO#Support_IPv6_network Anybody interested in implementing this?
I have updated our TODO item for this: https://pgpool.net/mediawiki/index.php/TODO#Support_IPv6_network Anybody interested in implementing this?
Oh, I forgot to reply this one.
As we talked on mail thread, This feature is implementing, ongoing.
For Just for a little bit informative to anyone...
https://www.pgpool.net/pipermail/pgpool-hackers/2024-July/004486.html
The feature will be on the next major release..
You also can check the thread with some detailed history.
https://www.pgpool.net/pipermail/pgpool-hackers/2024-August/004516.html
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?