doc: Mention pg_stat_wal_receiver in streaming replication docs

Also make the link to pg_stat_replication more precise.

Author: Michael Paquier 
Reviewed-by: Jeff Janes 

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index aa780d360dcb7b9d87555f433106968e8a17d3fd..6c0679b0a8b263950be068bbd8720073efc04c27 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -890,14 +890,20 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
     
     
      You can retrieve a list of WAL sender processes via the
-     
-     pg_stat_replication view. Large differences between
+      view. Large differences between
      pg_current_wal_lsn and the view's sent_lsn field
      might indicate that the master server is under heavy load, while
      differences between sent_lsn and
      pg_last_wal_receive_lsn on the standby might indicate
      network delay, or that the standby is under heavy load.
     
+    
+     On a hot standby, the status of the WAL receiver process can be retrieved
+     via the  view.  A large
+     difference between pg_last_wal_replay_lsn and the
+     view's received_lsn indicates that WAL is being
+     received faster than it can be replayed.
+