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

Modified Files:
	logshipping.sgml 
Log Message:
Fix tagging errors


Index: logshipping.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/logshipping.sgml,v
retrieving revision 1.18
retrieving revision 1.19
diff -C2 -d -r1.18 -r1.19
*** logshipping.sgml	3 Dec 2007 16:26:09 -0000	1.18
--- logshipping.sgml	11 Dec 2007 21:27:05 -0000	1.19
***************
*** 350,356 ****
  <indexterm><primary> trigger deactivation </primary> </indexterm>
  
! <para> It was once pointed out (<ulink> Bugzilla bug
  #19</ulink>) that the dump of a schema may include triggers and rules
! that you may not wish to have running on the log shipped node.
  
  <para> The tool <filename> tools/find-triggers-to-deactivate.sh
--- 350,357 ----
  <indexterm><primary> trigger deactivation </primary> </indexterm>
  
! <para> It was once pointed out (<ulink
! url="http://www.slony.info/bugzilla/show_bug.cgi?id=19"> Bugzilla bug
  #19</ulink>) that the dump of a schema may include triggers and rules
! that you may not wish to have running on the log shipped node.</para>
  
  <para> The tool <filename> tools/find-triggers-to-deactivate.sh
***************
*** 358,367 ****
  against the node that is to be used as a schema source, and it will
  list the rules and triggers present on that node that may, in turn
! need to be deactivated.
  
  <para> It includes <function>logtrigger</function> and <function>denyaccess</function>
  triggers which will may be left out of the extracted schema, but it is
  still worth the Gentle Administrator verifying that such triggers are
! kept out of the log shipped replica.</para></para></para>
  
  </sect2>
--- 359,368 ----
  against the node that is to be used as a schema source, and it will
  list the rules and triggers present on that node that may, in turn
! need to be deactivated.</para>
  
  <para> It includes <function>logtrigger</function> and <function>denyaccess</function>
  triggers which will may be left out of the extracted schema, but it is
  still worth the Gentle Administrator verifying that such triggers are
! kept out of the log shipped replica.</para>
  
  </sect2>