Log Message:
-----------
Fix SGML tagging error, add link so that Slonik reference pages
point to the FAQ entry on 'missing OIDs' problem

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        faq.sgml (r1.19 -> r1.20)
        slonik_ref.sgml (r1.12 -> r1.13)

-------------- next part --------------
Index: slonik_ref.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.12
retrieving revision 1.13
diff -Ldoc/adminguide/slonik_ref.sgml -Ldoc/adminguide/slonik_ref.sgml -u -w -r1.12 -r1.13
--- doc/adminguide/slonik_ref.sgml
+++ doc/adminguide/slonik_ref.sgml
@@ -405,6 +405,17 @@
       </varlistentry>
      </variablelist>
     </para>
+
+   <warning><para> If you are using connections that cache query plans
+   (this is particularly common for Java application frameworks with
+   connection pools), the connections may cache query plans that
+   include the pre-<command>DROP NODE</command> state of things, and
+   you will get <link linkend="missingoids"> error messages indicating
+   missing OIDs</link>.</para>
+
+   <para>After dropping a node, you may also need to recycle
+   connections in your application.</para></warning>
+
    </refsect1>
    <refsect1><title>Example</title>
     <programlisting>
@@ -440,6 +451,17 @@
       </varlistentry>
      </variablelist>
     </para>
+
+   <warning><para> If you are using connections that cache query plans
+   (this is particularly common for Java application frameworks with
+   connection pools), the connections may cache query plans that
+   include the pre-<command>UNINSTALL NODE</command> state of things,
+   and you will get <link linkend="missingoids"> error messages
+   indicating missing OIDs</link>.</para>
+
+   <para>After dropping a node, you may also need to recycle
+   connections in your application.</para></warning>
+
    </refsect1>
    <refsect1><title>Example</title>
     <programlisting>
Index: faq.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.19
retrieving revision 1.20
diff -Ldoc/adminguide/faq.sgml -Ldoc/adminguide/faq.sgml -u -w -r1.19 -r1.20
--- doc/adminguide/faq.sgml
+++ doc/adminguide/faq.sgml
@@ -1224,22 +1224,21 @@
 <answer><para> The problem is fairly self-evident; permission is being
 denied on the system table, <envar>pg_class</envar>.</para></answer>
 
-<answer><para> The <quote>fix</fix> is thus:
+<answer><para> The <quote>fix</quote> is thus:
 <programlisting>
 update pg_shadow set usesuper = 't', usecatupd='t' where usename = 'slony';
 </programlisting>
 </answer>
 </qandaentry>
 
-<qandaentry>
-<question> <para>
-We just got bitten by something we didn't foresee when completely
-uninstalling a slony replication cluster from the master and slave...</para>
-
-<warning> <para>MAKE SURE YOU STOP YOUR APPLICATION RUNNING AGAINST YOUR MASTER
-DATABASE WHEN REMOVING THE WHOLE SLONY CLUSTER, or at least re-cycle
-all your open connections after the event!
-</para></warning>
+<qandaentry id="missingoids"> <question> <para> We got bitten by
+something we didn't foresee when completely uninstalling a slony
+replication cluster from the master and slave...</para>
+
+<warning> <para><emphasis>MAKE SURE YOU STOP YOUR APPLICATION RUNNING
+AGAINST YOUR MASTER DATABASE WHEN REMOVING THE WHOLE SLONY
+CLUSTER</emphasis>, or at least re-cycle all your open connections
+after the event!  </para></warning>
 
 <para> The connections <quote>remember</quote> or refer to OIDs which
 are removed by the uninstall node script. And you get lots of errors