Log Message:
-----------
HEAD - add FAQ entry about cacheing of query plans causing pre-upgrade
versions of functions to be used.

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        faq.sgml (r1.66 -> r1.67)

-------------- next part --------------
Index: faq.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.66
retrieving revision 1.67
diff -Ldoc/adminguide/faq.sgml -Ldoc/adminguide/faq.sgml -u -w -r1.66 -r1.67
--- doc/adminguide/faq.sgml
+++ doc/adminguide/faq.sgml
@@ -348,6 +348,29 @@
 
 </qandaentry>
 
+<qandaentry><question><para> I upgraded my cluster to &slony1; version
+1.2.  I'm now getting the following notice in the logs:</para>
+
+<screen>NOTICE:  Slony-I: log switch to sl_log_2 still in progress - sl_log_1 not truncated</screen>
+
+<para> Both <envar>sl_log_1</envar> and <envar>sl_log_2</envar> are
+continuing to grow, and <envar>sl_log_1</envar> is never getting
+truncated.  What's wrong?
+</para> </question>
+
+<answer><para> This is symptomatic of the same issue as above with
+dropping replication: if there are still old connections lingering
+that are using old query plans that reference the old stored
+functions, resulting in the inserts to <envar>sl_log_1</envar> </para>
+
+<para> Closing those connections and opening new ones will resolve the
+issue. </para> </answer> 
+
+<answer> <para> In the longer term, there is an item on the &postgres;
+TODO list to implement dependancy checking that would flush cached
+query plans when dependent objects change.  </para> </answer>
+</qandaentry>
+
 <qandaentry>
 <question><para>I pointed a subscribing node to a different provider
 and it stopped replicating</para></question>