Log Message:
-----------
Indicate need to run "set drop table" queries on all nodes, perhaps
using EXECUTE SCRIPT.

Modified Files:
--------------
    slony1-engine/doc/howto:
        helpitsbroken.txt (r1.5 -> r1.6)

-------------- next part --------------
Index: helpitsbroken.txt
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/howto/helpitsbroken.txt,v
retrieving revision 1.5
retrieving revision 1.6
diff -Ldoc/howto/helpitsbroken.txt -Ldoc/howto/helpitsbroken.txt -u -w -r1.5 -r1.6
--- doc/howto/helpitsbroken.txt
+++ doc/howto/helpitsbroken.txt
@@ -199,3 +199,10 @@
 The schema will obviously depend on how you defined the Slony-I
 cluster.  The table ID, in this case, 40, will need to change to the
 ID of the table you want to have go away.
+
+You'll have to run these three queries on all of the nodes, preferably
+firstly on the "master" node, so that the dropping of this propagates
+properly.  Implementing this via a SLONIK statement with a new Slony
+event would do that.  Submitting the three queries using EXECUTE
+SCRIPT can do that.  Less ideal would be to connect to each database
+and submit the queries by hand.