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

Modified Files:
      Tag: REL_1_2_STABLE
	slon.sgml 
Log Message:
Per David Rees, made slon configuration documentation consistent with
defaults, and improved descriptions of sync_interval/sync_interval_timeout


Index: slon.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slon.sgml,v
retrieving revision 1.29.2.1
retrieving revision 1.29.2.2
diff -C2 -d -r1.29.2.1 -r1.29.2.2
*** slon.sgml	16 Mar 2007 19:01:26 -0000	1.29.2.1
--- slon.sgml	8 Aug 2007 15:23:30 -0000	1.29.2.2
***************
*** 80,84 ****
        indicates how often <application>slon</application> should check
        to see if a <command>SYNC</command> should be introduced.
!       Default is 10000 ms.  The main loop in
        <function>sync_Thread_main()</function> sleeps for intervals of
        <envar>sync_interval</envar> milliseconds between iterations.
--- 80,84 ----
        indicates how often <application>slon</application> should check
        to see if a <command>SYNC</command> should be introduced.
!       Default is 2000 ms.  The main loop in
        <function>sync_Thread_main()</function> sleeps for intervals of
        <envar>sync_interval</envar> milliseconds between iterations.
***************
*** 112,123 ****
        At the end of each <envar>sync_interval_timeout</envar> timeout
        period, a <command>SYNC</command> will be generated on the
!       <quote>local</quote> node even if there has been no replicatable
!       data updated that would have pushed out a
!       <command>SYNC</command>.
       </para>
       <para>
!       Default, and maximum, is 60000 ms, so that you can expect each
!       node to <quote>report in</quote> with a <command>SYNC</command>
!       once each minute.
       </para>
       <para>
--- 112,157 ----
        At the end of each <envar>sync_interval_timeout</envar> timeout
        period, a <command>SYNC</command> will be generated on the
!       <quote>local</quote> node even if there has been no replicable
!       data updated that would have caused a
!       <command>SYNC</command> to be generated. </para>
! 
!      <para> If application activity ceases, whether because the
!      application is shut down, or because human users have gone home
!      and stopped introducing updates, the &lslon; will iterate away,
!      waking up every <envar>sync_interval</envar> milliseconds, and,
!      as no updates are being made, no <command>SYNC</command> events
!      would be generated.  Without this timeout parameter,
!      <emphasis>no</emphasis> <command>SYNC</command> events would be
!      generated, and it would appear that replication was falling
!      behind. </para>
! 
!      <para> The <envar>sync_interval_timeout</envar> value will lead
!      to eventually generating a <command>SYNC</command>, even though
!      there was no real replication work to be done.  The lower that
!      this parameter is set, the more frequently &lslon; will generate
!      <command>SYNC</command> events when the application is not
!      generating replicable activity; this will have two effects:</para>
!       <itemizedlist>
! 
!       <listitem><para> The system will do more replication work.</para> 
! 
!       <para> (Of course, since there is no application load on the
!       database, and no data to replicate, this load will be very easy
!       to handle.  </para></listitem>
! 
!       <listitem><para> Replication will appear to be kept more
!       <quote>up to date.</quote></para>
! 
!       <para> (Of course, since there is no replicable activity going
!       on, being <quote>more up to date</quote> is something of a
!       mirage.) </para></listitem>
! 
!       </itemizedlist>
! 
       </para>
       <para>
!       Default is 10000 ms and maximum is 120000 ms. By default, you
!       can expect each node to <quote>report in</quote> with a
!       <command>SYNC</command> every 10 seconds.
       </para>
       <para>