Log Message:
-----------
The DDL_SCRIPT event is supported, with the result that log shipping
now _does_ cope with Slonik "execute script" requests.

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        logshipping.sgml (r1.3 -> r1.4)

-------------- next part --------------
Index: logshipping.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/logshipping.sgml,v
retrieving revision 1.3
retrieving revision 1.4
diff -Ldoc/adminguide/logshipping.sgml -Ldoc/adminguide/logshipping.sgml -u -w -r1.3 -r1.4
--- doc/adminguide/logshipping.sgml
+++ doc/adminguide/logshipping.sgml
@@ -118,25 +118,16 @@
 <emphasis>some</emphasis> changes in cluster configuration, but not
 others.  </para>
 
-<para> Log shipping does <emphasis>not</emphasis> submit events for
-<command> DDL_SCRIPT </command>, so if you do a DDL change via <link
-linkend="stmtddlscript"> <command>EXECUTE SCRIPT</command></link>, the
-script is not propagated.  It ought to be possible to address this via
-some changes to the <command>DDL_SCRIPT</command> event; a Simple
-Matter Of Programming... </para> 
-
-<para> But at present, the implication of this limitation is that the
-introduction of any of the following events can invalidate the
-relationship between the SYNCs and the dump created using
+<para> Log shipping does <emphasis>not</emphasis> process certain
+additional events, with the implication that the introduction of any
+of the following events can invalidate the relationship between the
+SYNCs and the dump created using
 <application>slony1_dump.sh</application> so that you'll likely need
 to rerun <application>slony1_dump.sh</application>:
 
 <itemizedlist>
 <listitem><para><command> SUBSCRIBE_SET </command> 
-<listitem><para><command> DDL_SCRIPT </command> 
 
-<para> It ought to be a <acronym>SMOP</acronym> to add a DDL script to
-the log shipping stream.
 </itemizedlist>
 
 <para> A number of event types <emphasis> are </emphasis> handled in
@@ -147,12 +138,14 @@
 <listitem><para><command>SYNC </command> events are, of course,
 handled.
 
+<listitem><para><command>DDL_SCRIPT</command> is handled.
+
 <listitem><para><command> UNSUBSCRIBE_SET </command> 
 
 <para> This event, much like <command>SUBSCRIBE_SET</command> is not
-handled by the log shipping code.  But its effect is, namely that SYNC
-events on the subscriber node will no longer contain updates to the
-set.
+handled by the log shipping code.  But its effect is, namely that
+<command>SYNC</command> events on the subscriber node will no longer
+contain updates to the set.
 
 <para> Similarly, <command>SET_DROP_TABLE</command>,
 <command>SET_DROP_SEQUENCE</command>,