Clarify that you can only monitor lag from an upstream
authorCraig Ringer <craig@2ndquadrant.com>
Mon, 20 Apr 2015 12:28:06 +0000 (20:28 +0800)
committerCraig Ringer <craig@2ndquadrant.com>
Mon, 20 Apr 2015 13:17:55 +0000 (21:17 +0800)
Per query from the mailing list,
http://www.postgresql.org/message-id/F38D1020-3B2C-41CF-BECD-1F1FB5B19806@visi.com

doc/manual-monitoring.sgml

index 5aef08614c1867967829ead22718ae626a81f014..940fb3b489773f0ea16c3a5cc7a99077f49fd6ad 100644 (file)
        pid, application_name
      FROM pg_stat_replication;
     </programlisting>
-    This will show lag for all replication consumers, including non-&bdr;
+    This query will show how much lag downstream servers have from the upstream
+    server you run the query on. You can't use this to see, from the downstream
+    server, how far it is behind an upstream it's receiving from.
+    Also, the query will show lag for all replication consumers, including non-&bdr;
     ones. To show only &bdr; peers, append
     <literal>WHERE application_name LIKE 'bdr%'</literal>.
    </para>