Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit ec7ce54

Browse files
committed
doc: Mention pg_stat_wal_receiver in streaming replication docs
Also make the link to pg_stat_replication more precise. Author: Michael Paquier <michael.paquier@gmail.com> Reviewed-by: Jeff Janes <jeff.janes@gmail.com>
1 parent af20e2d commit ec7ce54

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

doc/src/sgml/high-availability.sgml

+8-2
Original file line numberDiff line numberDiff line change
@@ -890,14 +890,20 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
890890
</para>
891891
<para>
892892
You can retrieve a list of WAL sender processes via the
893-
<link linkend="monitoring-stats-views-table">
894-
<literal>pg_stat_replication</literal></link> view. Large differences between
893+
<xref linkend="pg-stat-replication-view"> view. Large differences between
895894
<function>pg_current_wal_lsn</function> and the view's <literal>sent_lsn</literal> field
896895
might indicate that the master server is under heavy load, while
897896
differences between <literal>sent_lsn</literal> and
898897
<function>pg_last_wal_receive_lsn</function> on the standby might indicate
899898
network delay, or that the standby is under heavy load.
900899
</para>
900+
<para>
901+
On a hot standby, the status of the WAL receiver process can be retrieved
902+
via the <xref linkend="pg-stat-wal-receiver-view"> view. A large
903+
difference between <function>pg_last_wal_replay_lsn</function> and the
904+
view's <literal>received_lsn</literal> indicates that WAL is being
905+
received faster than it can be replayed.
906+
</para>
901907
</sect3>
902908
</sect2>
903909

0 commit comments

Comments
 (0)