earlier in this list, and
that are both currently connected and streaming data in real-time
(as shown by a state of <literal>streaming</literal> in the
- <link linkend="monitoring-stats-views-table">
+ <link linkend="pg-stat-replication-view">
<literal>pg_stat_replication</></link> view).
Other standby servers appearing later in this list represent potential
synchronous standbys. If any of the current synchronous
Specifies the minimum frequency for the WAL receiver
process on the standby to send information about replication progress
to the primary or upstream standby, where it can be seen using the
- <link linkend="monitoring-stats-views-table">
+ <link linkend="pg-stat-replication-view">
<literal>pg_stat_replication</></link> view. The standby will report
the last transaction log position it has written, the last position it
has flushed to disk, and the last position it has applied.
</para>
<para>
You can retrieve a list of WAL sender processes via the
- <link linkend="monitoring-stats-views-table">
+ <link linkend="pg-stat-replication-view">
<literal>pg_stat_replication</></link> view. Large differences between
<function>pg_current_xlog_location</> and <literal>sent_location</> field
might indicate that the master server is under heavy load, while
<listitem>
<para>
Add system view <link
- linkend="monitoring-stats-views-table"><structname>pg_stat_replication</></link>
+ linkend="pg-stat-replication-view"><structname>pg_stat_replication</></link>
which displays activity of <acronym>WAL</> sender processes (Itagaki
Takahiro, Simon Riggs)
</para>
-->
<para>
The <link
- linkend="monitoring-stats-views-table"><structname>pg_stat_replication</></link>
+ linkend="pg-stat-replication-view"><structname>pg_stat_replication</></link>
system view's <structfield>sent</> field is now NULL, not zero, when
it has no valid value (Magnus Hagander)
</para>