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

Modified Files:
	logshipping.sgml 
Log Message:
Add in script to support usage described in bug #19
<http://www.slony.info/bugzilla/show_bug.cgi?id=19>, including
documentation in admin guide.


Index: logshipping.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/logshipping.sgml,v
retrieving revision 1.17
retrieving revision 1.18
diff -C2 -d -r1.17 -r1.18
*** logshipping.sgml	10 Sep 2007 22:23:57 -0000	1.17
--- logshipping.sgml	3 Dec 2007 16:26:09 -0000	1.18
***************
*** 344,347 ****
--- 344,369 ----
  
  </sect2>
+ 
+ <sect2><title> <application> find-triggers-to-deactivate.sh
+ </application> </title>
+ 
+ <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
+ </filename> was created to assist with this task.  It may be run
+ 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>
  <sect2> <title> <application>slony_logshipper </application> Tool </title>