Log Message:
-----------
Added a couple of paragraphs to better explain the distinction between
DROP NODE and UNINSTALL NODE.

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        slonik_ref.sgml (r1.25 -> r1.26)

-------------- next part --------------
Index: slonik_ref.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.25
retrieving revision 1.26
diff -Ldoc/adminguide/slonik_ref.sgml -Ldoc/adminguide/slonik_ref.sgml -u -w -r1.25 -r1.26
--- doc/adminguide/slonik_ref.sgml
+++ doc/adminguide/slonik_ref.sgml
@@ -538,6 +538,9 @@
     <para> This uses <xref linkend=
     "function.dropnode-integer">. </para>
 
+    <para> When you invoke <command>DROP NODE</command>, one of the
+    steps is to run <command>UNINSTALL NODE</command>.</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
@@ -586,6 +589,11 @@
 
     <para> This uses <xref linkend= "function.uninstallnode">. </para>
 
+    <para> The difference between <command>UNINSTALL NODE</command>
+    and <command>DROP NODE</command> is that all <command>UNINSTALL
+    NODE</command> does is to remove the &slony1; configuration; it
+    doesn't drop the node's configuration from replication.</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