]> granicus.if.org Git - postgresql/commitdiff
doc: Fix links to pg_stat_replication
authorPeter Eisentraut <peter_e@gmx.net>
Sat, 3 Mar 2018 19:11:39 +0000 (14:11 -0500)
committerPeter Eisentraut <peter_e@gmx.net>
Sat, 3 Mar 2018 19:13:19 +0000 (14:13 -0500)
In PostgreSQL 9.5, the documentation for pg_stat_replication was moved,
so some of the links pointed to an appropriate location.

Author: Maksim Milyutin <milyutinma@gmail.com>

doc/src/sgml/config.sgml
doc/src/sgml/high-availability.sgml
doc/src/sgml/release-9.1.sgml
doc/src/sgml/release-9.5.sgml

index 388329fb10792007a744873d871428bc3e9d0680..e6bbe8af9836786c6e5cba36bb8b4a0750d1d8f2 100644 (file)
@@ -3035,7 +3035,7 @@ include_dir 'conf.d'
         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
@@ -3244,7 +3244,7 @@ include_dir 'conf.d'
        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.
index 774d2b4bce6356f69757da0a0e1732f077cd738c..3dc437df2465060b81ce55eae667be722a655868 100644 (file)
@@ -861,7 +861,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
     </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
index e1b1f3aab21bb0d5b8b5e1c2b32d2b2d8e4d5660..c4436713994ecaa9fb646b13d05d19631c520e39 100644 (file)
@@ -9667,7 +9667,7 @@ Branch: REL9_0_STABLE [9d6af7367] 2015-08-15 11:02:34 -0400
       <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>
index b6f16831ef582164431ffeda1656dd4340a70853..931332abf7fc74e31d3f66baf86efe9fe9c434f1 100644 (file)
@@ -6911,7 +6911,7 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
 -->
      <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>