Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv26686

Modified Files:
	slonik_ref.sgml 
Log Message:
Document a clever usage of STORE TRIGGER when the trigger is not yet
installed.

Per email from Andrew Sullivan...


Index: slonik_ref.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.68
retrieving revision 1.69
diff -C2 -d -r1.68 -r1.69
*** slonik_ref.sgml	18 Apr 2007 15:03:51 -0000	1.68
--- slonik_ref.sgml	24 Apr 2007 16:27:01 -0000	1.69
***************
*** 1833,1837 ****
       </variablelist>
      </para>
!     <para> This uses &funstoretrigger;. </para>
     </refsect1>
     <refsect1><title>Example</title>
--- 1833,1850 ----
       </variablelist>
      </para>
!     <note><para> A nifty trick is that you can run <command>STORE
!     TRIGGER</command> <emphasis>before the trigger is
!     installed;</emphasis> that will not cause any errors.  You could
!     thus add &slony1;'s handling of the trigger
!     <emphasis>before</emphasis> it is installed.  That allows you to
!     be certain that it becomes active on all nodes immediately upon
!     its installation via <xref linkend="stmtddlscript">; there is no
!     risk of events getting through in between the <command>EXECUTE
!     SCRIPT</command> and <command>STORE TRIGGER</command>
!     events. </para>
!     </note>
! 
!    <para> This uses
!     &funstoretrigger;. </para>
     </refsect1>
     <refsect1><title>Example</title>
***************
*** 1847,1851 ****
      <para> This operation will need to acquire an exclusive lock on
      the specified table on each node to which it applies in order to
!     alter table schemas to add back the trigger. </para>
     </refsect1>
     <refsect1> <title> Version Information </title>
--- 1860,1864 ----
      <para> This operation will need to acquire an exclusive lock on
      the specified table on each node to which it applies in order to
!     alter table schemas to add back the trigger, but only briefly. </para>
     </refsect1>
     <refsect1> <title> Version Information </title>