http://www.slony.info/bugzilla/show_bug.cgi?id=126

Steve Singer <ssinger at ca.afilias.info> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #7 from Steve Singer <ssinger at ca.afilias.info> 2011-01-06 12:37:08 PST ---
I have a fix for this bug available in the attached patches or at
https://github.com/ssinger/slony1-engine/tree/bug126

The github branch has all three patches applied. (The fix is pretty useless
without the typing issue fixed).

An item that showed up in my testing that is worth thinking about.

If the network connection between the slon and the local node goes away the
slon will exit (I think this is what we want) but it then restarts and keeps
looping trying to connect to the local node (again this is what we want).

However if when the network comes back and it connects to the postgres
instance, IF the timeout settings on the postgresql side are such that the  old
backend has not yet timed out then a sl_nodelock row will exist.  The slon will
then exit on an error (and not retry).

I'm not sure this is the result we want. In bug132 we made the slon loop on
getting the node lock IF it could not get the node lock due to a slon requested
restart.  In this case we are restarting due to a slon error.  I'm not sure if
we want to change this behavior or not.

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.