1. The update sl_subscribe statement was duplicated,
   the exact same SQL was listed twice.
2. Do not delete the sl_subscribe row for the backup node.
   We were finding that a slave could end up with data the
   backup node did not have when it became a master because
   the backup node was ignoring the sync because it didn't
   think it had a provider.

This reverts parts of d50fba024aac79020549973e98a4ea9d5bccdab5
(cherry picked from commit 7970189ec93faf3ee71cf49e97529980bbd219aa)

Branch
------
master

Details
-------
http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=a59aaab94d84e5ac79b0757068577b78cc4990e3

Modified Files
--------------
src/backend/slony1_funcs.sql |   20 ++------------------
1 files changed, 2 insertions(+), 18 deletions(-)