Chris Browne cbbrowne at lists.slony.info
Wed Aug 22 15:05:50 PDT 2007
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv2367

Modified Files:
	slonyupgrade.sgml 
Log Message:
Beginnings of discussion of trigger handling changes in Slony-I 2.0


Index: slonyupgrade.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slonyupgrade.sgml,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** slonyupgrade.sgml	9 Jul 2007 15:19:49 -0000	1.7
--- slonyupgrade.sgml	22 Aug 2007 22:05:48 -0000	1.8
***************
*** 238,241 ****
--- 238,254 ----
  
  </sect2>
+ 
+ <sect2> <title> New Trigger Handling in &slony1; Version 2 </title>
+ 
+ <para> One of the major changes to &slony1; is that enabling/disabling
+ of triggers and rules now takes place as plain SQL, supported by
+ &postgres; 8.3+, rather than via <quote>hacking</quote> on the system
+ catalog. </para>
+ 
+ <para> As a result, &slony1; users should be aware of the &postgres;
+ syntax for <command>ALTER TABLE</command>, as that is how they can
+ accomplish what was formerly accomplished via <xref
+ linkend="stmtstoretrigger"> and <xref linkend="stmtdroptrigger">. </para>
+ 
  </sect1>
  <!-- Keep this comment at the end of the file



More information about the Slony1-commit mailing list