Log Message:
-----------
Best practice change - dropping/reindexing of tables is now available
in Slony-I 1.1.5...

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

-------------- next part --------------
Index: bestpractices.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/bestpractices.sgml,v
retrieving revision 1.17
retrieving revision 1.18
diff -Ldoc/adminguide/bestpractices.sgml -Ldoc/adminguide/bestpractices.sgml -u -w -r1.17 -r1.18
--- doc/adminguide/bestpractices.sgml
+++ doc/adminguide/bestpractices.sgml
@@ -451,8 +451,9 @@
 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 &slony1; version 1.1.5 and later versions, indices are
+dropped and recreated automatically, which mostly eliminates the need
+for this.</para>
 </listitem>
 
 <listitem><para> If there are large numbers of updates taking place as