From c5e8ea978d88ea4aa731516836e14d54c50cc957 Mon Sep 17 00:00:00 2001
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: Tue, 12 Nov 2019 18:34:20 -0300
Subject: [PATCH] pg_stat_activity: document client_port being null

As suggested by Stephen Frost.
Discussion: https://postgr.es/m/20191104160605.GC6962@tamriel.snowman.net
---
 doc/src/sgml/monitoring.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index d18b271a58..901fee97ff 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -652,7 +652,8 @@ postgres   27093  0.0  0.0  30096  2752 ?        Ss   11:34   0:00 postgres: ser
      <entry><structfield>client_port</structfield></entry>
      <entry><type>integer</type></entry>
      <entry>TCP port number that the client is using for communication
-      with this backend, or <literal>-1</literal> if a Unix socket is used
+      with this backend, or <literal>-1</literal> if a Unix socket is used.
+      If this field is null, it indicates that this is an internal server process.
      </entry>
     </row>
     <row>