From: Craig Ringer <craig@2ndquadrant.com>
Date: Mon, 20 Apr 2015 12:28:06 +0000 (+0800)
Subject: Clarify that you can only monitor lag from an upstream
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=aee468e2b3661ca62847707f4feca49406c60f1b;p=2ndquadrant_bdr.git

Clarify that you can only monitor lag from an upstream

Per query from the mailing list,
http://www.postgresql.org/message-id/F38D1020-3B2C-41CF-BECD-1F1FB5B19806@visi.com
---

diff --git a/doc/manual-monitoring.sgml b/doc/manual-monitoring.sgml
index 5aef08614c..940fb3b489 100644
--- a/doc/manual-monitoring.sgml
+++ b/doc/manual-monitoring.sgml
@@ -144,7 +144,10 @@
        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>