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

Modified Files:
	triggers.sgml 
Log Message:
Improve trigger documentation for v2.0


Index: triggers.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/triggers.sgml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** triggers.sgml	28 Jan 2008 19:35:21 -0000	1.1
--- triggers.sgml	18 Apr 2008 16:53:11 -0000	1.2
***************
*** 138,146 ****
  
  <para> This may be expected to allow DDL changes to become
! <emphasis>enormously</emphasis> less expensive, since, rather than needing to
! take out exclusive locks on <emphasis>all</emphasis> replicated tables (as used
! to be mandated by the action of dropping and adding back the
! &slony1;-created triggers), the only tables that are locked are those
! ones that the DDL script was specifically acting on.  </para>
  
  </listitem>
--- 138,147 ----
  
  <para> This may be expected to allow DDL changes to become
! <emphasis>enormously</emphasis> less expensive, since, rather than
! needing to take out exclusive locks on <emphasis>all</emphasis>
! replicated tables (as used to be mandated by the action of dropping
! and adding back the &slony1;-created triggers), the only tables that
! are locked are those ones that the DDL script was specifically acting
! on.  </para>
  
  </listitem>
***************
*** 159,164 ****
  
  <para> From a locking perspective, this will not behave differently
! from older versions of &slony1;; the locking that takes place here is
! quite necessary. </para>
  
  </listitem>
--- 160,166 ----
  
  <para> From a locking perspective, this will not behave differently
! from older versions of &slony1;; to disable and enable the respective
! triggers requires taking out exclusive locks on all replicated
! tables. </para>
  
  </listitem>
***************
*** 169,173 ****
  <function>denyaccess</function> triggers, and enabling the
  <function>logtrigger</function> triggers.  The locking implications
! are again, much the same.  </para> </listitem>
  
  </itemizedlist>
--- 171,176 ----
  <function>denyaccess</function> triggers, and enabling the
  <function>logtrigger</function> triggers.  The locking implications
! are again, much the same, requiring an exclusive lock on each such
! table.  </para> </listitem>
  
  </itemizedlist>