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

Log Message
-----------
Bug 136
    When a forwarding node goes away a dba might issue a subscribe set to reshape the
    cluster so the receiver gets the data from a different provider.
    It could be the case that the receiver never sees the SUBSCRIBE_SET event
    because it is only listening on events from the origin from the forwarder
    that has gone away.

    If we are reshaping a cluster then slonik will contact the receiver
    directly and run update sl_subscribe so the receiver can
    listen from the correct source.
(cherry picked from commit 0f8305660488d508df6a6ea96bf8ebf57e2e77ea)

Conflicts:

	src/backend/slony1_funcs.sql

Branch
------
master

Modified Files
--------------
src/backend/slony1_funcs.sql |   25 ++++++++++++++++++
src/slonik/slonik.c          |   56 ++++++++++++++++++++++++++++++++++++++++-
2 files changed, 79 insertions(+), 2 deletions(-)