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

Modified Files:
	bestpractices.sgml 
Log Message:
Add in note about increasing sync interval when running long subscriptions


Index: bestpractices.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/bestpractices.sgml,v
retrieving revision 1.33
retrieving revision 1.34
diff -C2 -d -r1.33 -r1.34
*** bestpractices.sgml	24 Mar 2008 15:57:34 -0000	1.33
--- bestpractices.sgml	21 Apr 2008 21:31:23 -0000	1.34
***************
*** 300,305 ****
  lock on them; doing so via <command>execute script</command> requires
  that &slony1; take out an exclusive lock on <emphasis>all</emphasis>
! replicated tables.  This can prove quite inconvenient when
! applications are running; you run into deadlocks and such. </para>
  
  <para> One particularly dogmatic position that some hold is that
--- 300,308 ----
  lock on them; doing so via <command>execute script</command> requires
  that &slony1; take out an exclusive lock on <emphasis>all</emphasis>
! replicated tables.  This can prove quite inconvenient if applications
! are running when running DDL; &slony1; is asking for those exclusive
! table locks, whilst, simultaneously, some application connections are
! gradually relinquishing locks, whilst others are backing up behind the
! &slony1; locks.  </para>
  
  <para> One particularly dogmatic position that some hold is that
***************
*** 516,519 ****
--- 519,531 ----
  user out of the new subscriber because:
  </para>
+ 
+ <para> It is also a very good idea to change &lslon; configuration for
+ <xref linkend="slon-config-sync-interval"> on the origin node to
+ reduce how many <command>SYNC</command> events are generated.  If the
+ subscription takes 8 hours, there is little sense in there being 28800
+ <command>SYNC</command>s waiting to be applied.  Running a
+ <command>SYNC</command> every minute or so is likely to make catching
+ up easier.</para>
+ 
  </listitem>
  </itemizedlist>