Log Message:
-----------
Add a discussion of the need for an index on sl_log_1(log_xid) to both
the "best practices" section and the FAQ.

Tags:
----
REL_1_1_STABLE

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        bestpractices.sgml (r1.9 -> r1.9.2.1)
        faq.sgml (r1.40 -> r1.40.2.1)

-------------- next part --------------
Index: bestpractices.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/bestpractices.sgml,v
retrieving revision 1.9
retrieving revision 1.9.2.1
diff -Ldoc/adminguide/bestpractices.sgml -Ldoc/adminguide/bestpractices.sgml -u -w -r1.9 -r1.9.2.1
--- doc/adminguide/bestpractices.sgml
+++ doc/adminguide/bestpractices.sgml
@@ -326,8 +326,8 @@
 recreating each index <quote>ex nihilo</quote>, as the latter can take
 substantial advantage of sort memory. </para>
 
-<para> In a future release, it is hopeful that indices will be dropped
-and recreated automatically, which would eliminate this.</para>
+<para> In version 1.2, indices will be dropped and recreated
+automatically, which would make this unnecessary.</para>
 </listitem>
 
 <listitem><para> If there are large numbers of updates taking place as
@@ -357,6 +357,12 @@
 </itemizedlist>
 <itemizedlist>
 
+<listitem><para> Ensure that there exists, on the
+<quote>master</quote> node, an index on <function> sl_log_1(log_xid)
+</function>.  If it doesn't exist, as the &slony1; instance was set up
+before version 1.1.1, see <filename> slony1_base.sql </filename> for
+the exact form that the index setup should take. </para> </listitem>
+
 <listitem><para> On the subscriber's <xref linkend="slon">, increase
 the number of <command>SYNC</command> events processed together, with
 the <xref linkend= "slon-config-sync-group-maxsize"> parameter to some
@@ -384,6 +390,7 @@
 vacuum scripts, as there will be a buildup of unpurgeable data while
 the data is copied and the subscriber starts to catch up. </para>
 </listitem>
+
 </itemizedlist>
 
 </sect1>
Index: faq.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.40
retrieving revision 1.40.2.1
diff -Ldoc/adminguide/faq.sgml -Ldoc/adminguide/faq.sgml -u -w -r1.40 -r1.40.2.1
--- doc/adminguide/faq.sgml
+++ doc/adminguide/faq.sgml
@@ -1590,6 +1590,24 @@
 comfortable with &postgres; and &slony1; that you are prepared to hack
 pretty heavily with the code.  </para> </answer>
 </qandaentry>
+
+<qandaentry>
+<question> <para> Replication has fallen behind, and it appears that the
+queries to draw data from <xref linkend="table.sl-log-1">/<xref
+linkend="table.sl-log-2"> are taking a long time to pull just a few
+<command>SYNC</command>s. </para>
+</question>
+
+<answer> <para> Until version 1.1.1, there was only one index on <xref
+linkend="table.sl-log-1">/<xref linkend="table.sl-log-2">, and if
+there were multiple replication sets, some of the columns on the index
+would not provide meaningful selectivity.  If there is no index on
+column <function> log_xid</function>, consider adding it.  See
+<filename>slony1_base.sql</filename> for an example of how to create
+the index.
+</para>
+</answer>
+</qandaentry>
 </qandaset>
 
 <!-- Keep this comment at the end of the file Local variables: