Chris Browne cbbrowne at lists.slony.info
Tue Mar 11 08:56:02 PDT 2008
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv1363

Modified Files:
	bestpractices.sgml 
Log Message:
Indicate frequent use of test_slony_state.pl as a Good Idea...


Index: bestpractices.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/bestpractices.sgml,v
retrieving revision 1.31
retrieving revision 1.32
diff -C2 -d -r1.31 -r1.32
*** bestpractices.sgml	27 Feb 2008 19:37:03 -0000	1.31
--- bestpractices.sgml	11 Mar 2008 15:56:00 -0000	1.32
***************
*** 462,465 ****
--- 462,471 ----
  tool can run through many of the possible problems for you. </para>
  
+ <para> It will also notice a number of sorts of situations where
+ something has broken.  Not only should it be run when problems have
+ been noticed - it should be run frequently (<emphasis>e.g.</emphasis>
+ - hourly, or thereabouts) as a general purpose <quote>health
+ check</quote> for each &slony1; cluster. </para>
+ 
  </listitem>
  



More information about the Slony1-commit mailing list