Add client_hostname field to pg_stat_activity.

Peter Eisentraut, reviewed by Steve Singer, Alvaro Herrera, and me.

1 files changed, 19 insertions, 12 deletions

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 58e3459e678..2dc1bfc19c7 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -245,14 +245,17 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
       <entry><structname>pg_stat_activity</><indexterm><primary>pg_stat_activity</primary></indexterm></entry>
       <entry>One row per server process, showing database OID, database
       name, process <acronym>ID</>, user OID, user name, application name,
-      client's address and port number, times at which the server process,
-      current transaction, and current query began execution, process's waiting
-      status, and text of the current query.
+      client's address, hostname (if available), and port number, times at
+      which the server process, current transaction, and current query began
+      execution, process's waiting status, and text of the current query.
       The columns that report data on the current query are available unless
       the parameter <varname>track_activities</varname> has been turned off.
       Furthermore, these columns are only visible if the user examining
       the view is a superuser or the same as the user owning the process
-      being reported on.
+      being reported on.  The client's hostname will be available only if
+      <xref linkend="guc-log-hostname"> is set or if the user's hostname
+      needed to be looked up during <filename>pg_hba.conf</filename>
+      processing.
      </entry>
      </row>
 
@@ -297,14 +300,18 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
      <row>
       <entry><structname>pg_stat_replication</><indexterm><primary>pg_stat_replication</primary></indexterm></entry>
       <entry>One row per WAL sender process, showing process <acronym>ID</>,
-      user OID, user name, application name, client's address and port number,
-      time at which the server process began execution, and the current WAL
-      sender state and transaction log location.  In addition, the standby
-      reports the last transaction log position it received and wrote, the last
-      position it flushed to disk, and the last position it replayed, and this
-      information is also displayed here.  The columns detailing what exactly
-      the connection is doing are only visible if the user examining the view
-      is a superuser.
+      user OID, user name, application name, client's address, hostname
+      (if available) and port number, time at which the server process began
+      execution, and the current WAL sender state and transaction log
+      location.  In addition, the standby reports the last transaction log
+      position it received and wrote, the last position it flushed to disk,
+      and the last position it replayed, and this information is also
+      displayed here.  The columns detailing what exactly the connection is
+      doing are only visible if the user examining the view is a superuser.
+      The client's hostname will be available only if
+      <xref linkend="guc-log-hostname"> is set or if the user's hostname
+      needed to be looked up during <filename>pg_hba.conf</filename>
+      processing.
      </entry>
      </row>