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

Modified Files:
	slonik_ref.sgml 
Log Message:
Clarify the discussion about the need to regenerate logtriggers on replicated
tables as part of EXECUTE SCRIPT...

Per question by Bill Moran...


Index: slonik_ref.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.82
retrieving revision 1.83
diff -C2 -d -r1.82 -r1.83
*** slonik_ref.sgml	11 Mar 2008 15:55:13 -0000	1.82
--- slonik_ref.sgml	27 Mar 2008 19:55:40 -0000	1.83
***************
*** 2628,2638 ****
      <para> See also the warnings in &rddlchanges;.</para>
  
!     <para> Note that this is a &rlocking; operation, which means that
!     it can get stuck behind other database activity.</para>
       
!     <para> At the start of this event, all replicated tables are
!     unlocked via the function
!     <function>alterTableRestore(tab_id)</function>.  After the SQL
!     script has run, they are returned to <quote>replicating
      state</quote> using
      <function>alterTableForReplication(tab_id)</function>.  This means
--- 2628,2639 ----
      <para> See also the warnings in &rddlchanges;.</para>
  
!     <para> Note that this is a potentially heavily-&rlocking;
!     operation, which means that it can get stuck behind other database
!     activity.</para>
       
!     <para> In versions up to (and including) the 1.2 branch, at the
!     start of this event, all replicated tables are unlocked via the
!     function <function>alterTableRestore(tab_id)</function>.  After
!     the SQL script has run, they are returned to <quote>replicating
      state</quote> using
      <function>alterTableForReplication(tab_id)</function>.  This means
***************
*** 2640,2646 ****
      duration of the SQL script execution.</para>
  
!     <para> If a table's columns are modified, it is very important
!     that the triggers be regenerated, otherwise they may be
!     inappropriate for the new form of the table schema.</para>
  
      <para> Note that if you need to make reference to the cluster
--- 2641,2649 ----
      duration of the SQL script execution.</para>
  
!     <para> If a table's columns are modified, it is essential that the
!     triggers be regenerated (<emphasis>e.g.</emphasis> - by
!     <function>alterTableForReplication(tab_id)</function>), otherwise
!     the attributes in the <function>logtrigger()</function> trigger
!     may be inappropriate for the new form of the table schema.</para>
  
      <para> Note that if you need to make reference to the cluster