Log Message:
-----------
Bug #1522 - EXECUTE SCRIPT locks all tables...

Add documentation to indicate that EXECUTE SCRIPT will lock tables 
across ALL sets, not just the one specified.

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

-------------- next part --------------
Index: slonik_ref.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.55
retrieving revision 1.56
diff -Ldoc/adminguide/slonik_ref.sgml -Ldoc/adminguide/slonik_ref.sgml -u -w -r1.55 -r1.56
--- doc/adminguide/slonik_ref.sgml
+++ doc/adminguide/slonik_ref.sgml
@@ -2478,15 +2478,14 @@
     <para> Note that this is a &rlocking; operation, which means that
     it can get stuck behind other database activity.</para>
      
-    <para> At the start of this event, all tables in the specified set
-    are unlocked via the function
+    <para> At the start of this event, all replicated tables are
+    unlocked via the function
     <function>alterTableRestore(tab_id)</function>.  After the SQL
     script has run, they are returned to <quote>replicating
     state</quote> using
     <function>alterTableForReplication(tab_id)</function>.  This means
-    that all of these tables are locked by this <application> slon
-    </application> process for the duration of the SQL script
-    execution.</para>
+    that all of these tables are locked by this &lslon process for the
+    duration of the SQL script execution.</para>
 
     <para> If a table's columns are modified, it is very important
     that the triggers be regenerated, otherwise they may be
@@ -2542,6 +2541,13 @@
     includes a listing of each statement as it is processed, on the
     set origin node.  Similarly, the statements processed are listed
     in slon logs on the other nodes.</para>
+
+    <para> In &slony1; version 1.0, this would only lock the tables in
+    the specified replication set.  As of 1.1, <emphasis>all
+    replicated tables</emphasis> are locked (<emphasis>e.g.</emphasis>
+    - triggers are removed at the start, and restored at the end).
+    This deals with the risk that one might request DDL changes on
+    tables in multiple replication sets.</para>
    </refsect1>
   </refentry>