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

Modified Files:
	defineset.sgml 
Log Message:
Comment on another reason (CONNECTION TIMEOUT) to separate a large
replication set into multiple pieces.


Index: defineset.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/defineset.sgml,v
retrieving revision 1.28
retrieving revision 1.29
diff -C2 -d -r1.28 -r1.29
*** defineset.sgml	11 Jun 2007 16:02:50 -0000	1.28
--- defineset.sgml	4 Feb 2008 20:56:22 -0000	1.29
***************
*** 121,124 ****
--- 121,134 ----
  the degree of the <quote>injury</quote> to performance.</para>
  
+ <para> Another issue comes up particularly frequently when replicating
+ across a WAN; sometimes the network connection is a little bit
+ unstable, such that there is a risk that a connection held open for
+ several hours will lead to <command>CONNECTION TIMEOUT.</command> If
+ that happens when 95% done copying a 50-table replication set
+ consisting of 250GB of data, that could ruin your whole day.  If the
+ tables were, instead, associated with separate replication sets, that
+ failure at the 95% point might only interrupt, temporarily, the
+ copying of <emphasis>one</emphasis> of those tables.  </para>
+ 
  <para> These <quote>negative effects</quote> tend to emerge when the
  database being subscribed to is many gigabytes in size and where it