Re: Enhance pg_stat_wal_receiver view to display connected host
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Haribabu Kommi <kommi.haribabu@gmail.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>, Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: 2018-01-30T05:02:26Z
Lists: pgsql-hackers
On Tue, Jan 30, 2018 at 03:10:12PM +1100, Haribabu Kommi wrote: > Ok, understood. As the libpq gives preference to hostaddr connection > parameter than host while connecting. How about going with one column > "remote_host" that displays either hostaddr(if exists) or hostname. So that > one column that displays the actual remote host to where it connected? > > Note : The one column approach for both host and hostaddr will depend on > how we go with PQhostaddr() function. Yeah, we don't want to begin a open battle for that. Using one column as a first step would still be useful anyway. If the discussion about PQhostaddr() comes to a result at some point, then it could make sense to integrate that with pg_stat_wal_receiver. The problem with PQhost handling strangely multiple host values is inconsistent though. > OK. I will move the patch to next commitfest. Thanks. Let's see what others think on all those threads. -- Michael
Commits
-
Enhance pg_stat_wal_receiver view to display host and port of sender server.
- 9a895462d940 11.0 landed
-
Allow multiple hostaddrs to go with multiple hostnames.
- 7b02ba62e9ff 10.0 cited
-
libpq: Fix inadvertent change in PQhost() behavior.
- 11003eb55658 10.0 cited
-
libpq: Allow connection strings and URIs to specify multiple hosts.
- 274bb2b3857c 10.0 cited