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

Modified Files:
	triggers.sgml 
Log Message:
Fix sgml errors


Index: triggers.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/triggers.sgml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** triggers.sgml	18 Apr 2008 16:53:11 -0000	1.2
--- triggers.sgml	13 Oct 2008 21:36:45 -0000	1.3
***************
*** 5,9 ****
  
  <para> &slony1; has had two <quote>flavours</quote> of trigger
! handling:
  <itemizedlist>
  
--- 5,9 ----
  
  <para> &slony1; has had two <quote>flavours</quote> of trigger
! handling:</para>
  <itemizedlist>
  
***************
*** 11,15 ****
  replication, with the result that &slony1; needed to
  <quote>hack</quote> on the system catalog in order to deactivate, on
! subscribers, triggers that ought not to run.</para>
  
  <para> This has had a number of somewhat painful side-effects including:</para> 
--- 11,16 ----
  replication, with the result that &slony1; needed to
  <quote>hack</quote> on the system catalog in order to deactivate, on
! subscribers, triggers that ought not to run.</para></listitem>
! </itemizedlist>
  
  <para> This has had a number of somewhat painful side-effects including:</para> 
***************
*** 36,43 ****
  </itemizedlist>
  
  <listitem><para> In &postgres; version 8.3, there is new functionality
  where triggers and rules can have their behaviour altered via
  <command>ALTER TABLE</command>, and specify any of the following
! further trigger-related options:</para>
  
  <itemizedlist>
--- 37,48 ----
  </itemizedlist>
  
+ <itemizedlist>
+ 
  <listitem><para> In &postgres; version 8.3, there is new functionality
  where triggers and rules can have their behaviour altered via
  <command>ALTER TABLE</command>, and specify any of the following
! further trigger-related options:</para></listitem>
! 
! </itemizedlist>
  
  <itemizedlist>
***************
*** 61,65 ****
  <para> We may characterize when triggers fire, under &slony1;
  replication, based on the following table; the same rules apply to
! &postgres; rules.
  
  <table id="triggerbehaviour"> <title> Trigger Behaviour </title>
--- 66,70 ----
  <para> We may characterize when triggers fire, under &slony1;
  replication, based on the following table; the same rules apply to
! &postgres; rules.</para>
  
  <table id="triggerbehaviour"> <title> Trigger Behaviour </title>
***************
*** 74,77 ****
--- 79,84 ----
  <row> <entry>ENABLE ALWAYS TRIGGER</entry> <entry>User request</entry> <entry>inappropriate</entry> <entry>inappropriate</entry> <entry>fires</entry>  <entry>fires</entry>  <entry>fires</entry> </row>
  </tbody>
+ </tgroup>
+ </table>
  
  <para> There are, correspondingly, now, several ways in which &slony1;