From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: Enhance pg_stat_wal_receiver view to display connected host |
Date: | 2018-01-30 05:02:26 |
Message-ID: | 20180130050226.GE27287@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Yugo Nagata | 2018-01-30 05:17:11 | Re: [HACKERS] [PATCH] Lockable views |
Previous Message | Tatsuo Ishii | 2018-01-30 04:58:30 | Re: [HACKERS] [PATCH] Lockable views |