Log Message:
-----------
Documentation was unclear; the problem with 'big sets' leading to
'long running transactions' occurs at the time of the COPY_SET event,
not during normal operations of SYNCs.

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        defineset.sgml (r1.16 -> r1.17)

-------------- next part --------------
Index: defineset.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/defineset.sgml,v
retrieving revision 1.16
retrieving revision 1.17
diff -Ldoc/adminguide/defineset.sgml -Ldoc/adminguide/defineset.sgml -u -w -r1.16 -r1.17
--- doc/adminguide/defineset.sgml
+++ doc/adminguide/defineset.sgml
@@ -85,15 +85,15 @@
 
 <itemizedlist>
 
-<listitem><para> Replicating a large set leads to a <link
-       linkend="longtxnsareevil"> long running transaction </link> on the
-provider node.  <xref linkend="faq"> outlines a number of problems
-that result from long running transactions that will injure system
-performance.</para>
-
-<para> If you can split a large set into several pieces, that will
-shorten the length of each of the transactions, lessening the degree
-of <quote>injury</quote> to performance.</para></listitem>
+<listitem><para> The initial <command>COPY_SET</command> event for a
+large set leads to a <link linkend="longtxnsareevil"> long running
+transaction </link> on the provider node.  The <link linkend="faq">
+FAQ </link> outlines a number of problems that result from long
+running transactions that will injure system performance.</para>
+
+<para> If you can split such a large set into several smaller pieces,
+that will shorten the length of each of the transactions, lessening
+the degree of <quote>injury</quote> to performance.</para></listitem>
 
 <listitem><para> Any time you invoke <xref linkend="stmtddlscript">,
 this requests a lock on <emphasis> every single table in the