Log Message:
-----------
Release Notes: Add in discussion of "slon not fall over easy no more"

Modified Files:
--------------
    slony1-engine:
        RELEASE-1.2.0 (r1.4 -> r1.5)

-------------- next part --------------
Index: RELEASE-1.2.0
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/RELEASE-1.2.0,v
retrieving revision 1.4
retrieving revision 1.5
diff -LRELEASE-1.2.0 -LRELEASE-1.2.0 -u -w -r1.4 -r1.5
--- RELEASE-1.2.0
+++ RELEASE-1.2.0
@@ -64,6 +64,22 @@
   A group of developers has contributed changes to allow running
   Slony-I as a Windows service.
 
+- Process structure is revised considerably; in 1.1.0, an attempt was
+  made to create an internal 'watchdog' that would restart threads
+  that fell over for whatever reason.
+
+  In 1.2, this is massively revised.  The "main" slon thread should,
+  as of 1.2, never fall down, which means that there should no longer
+  be a need for watchdog processes to watch carefully.
+
+  This makes slon very much less fragile than it was in earlier
+  versions.  This may revise how you want to start it up...  In the
+  past, slon processes tended to fall over easily, mandating having
+  some form of "watchdog."  The new behaviour points more towards
+  "init" / "rc.d"-like handling, where, upon bootup, one "rc.d" script
+  might start up PostgreSQL, another one starts pgpool, and a third
+  (which must run third!) starts up a slon.
+
 - Subscribe set aggressively locks tables on the subscriber to avoid
   failures