Log Message:
-----------
Note in slon documentation the downside to using the "lag interval"

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        slon.sgml (r1.25 -> r1.26)

-------------- next part --------------
Index: slon.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slon.sgml,v
retrieving revision 1.25
retrieving revision 1.26
diff -Ldoc/adminguide/slon.sgml -Ldoc/adminguide/slon.sgml -u -w -r1.25 -r1.26
--- doc/adminguide/slon.sgml
+++ doc/adminguide/slon.sgml
@@ -342,6 +342,16 @@
       causes events to be ignored until they reach the age
       corresponding to the interval.
      </para>
+
+     <warning><para> There is a concommittant downside to this lag;
+     events that require all nodes to synchronize, as typically
+     happens with <xref linkend="stmtfailover"> and <xref
+     linkend="stmtmoveset">, will have to wait for this lagging
+     node. </para>
+
+     <para> That might not be ideal behaviour at failover time, or at
+     the time when you want to run <xref
+     linkend="stmtddlscript">. </para></warning>
     </listitem>
    </varlistentry>