Hello Slony-I community,
                We’re working on a postgres upgrade now and considering a slony 2.2.4 to 2.2.6 upgrade to perform at the same time. I’ve found the Slony-I Upgrade section in the doc. This describes an all-at-once upgrade procedure which is difficult for us. For a 2.2.4 to 2.2.6 upgrade, what would be the barriers to upgrading each node in turn? Of course we’ve seen the schema check in remote_listen.c. However, the 2.2.6 upgradeSchema function looks like it has little or no work to do. Setting aside the schema check, are there any data format or other problems which would prevent 2.2.4 from replicating from 2.2.6 or vice versa?

                Tom    ☺


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20171113/473d735a/attachment.htm