Thu Jun 6 01:16:56 PDT 2013
- Previous message: [Slony1-general] Slony Versions and Postgres Versions and the compatibility.
- Next message: [Slony1-general] Slony Versions and Postgres Versions and the compatibility.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> > > ** > > Is there a Hard Rule that the Slony versions must be 100% exact at all > times, or can a Target Node be at a newer subversion ahead of the Master > and still run. > AFAIK, Slony-I need exact version on both the node's. Because upgrading a node to newer version will do changes to slony_func.so file where it should match the version with the other replicating nodes else it will break. Below link has a comment after the upgrade steps as " If there is any mismatch between component versions, the slon<http://main.slony.info/documentation/2.1/slon.html> will refuse to start up, which provides protection against corruption." http://main.slony.info/documentation/2.1/slonyupgrade.html For your other questions, hopefully you will see some answer's here. -- Regards Raghav Blog: htt://raghavt.blogspot.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20130606/82bee8a6/attachment.htm
- Previous message: [Slony1-general] Slony Versions and Postgres Versions and the compatibility.
- Next message: [Slony1-general] Slony Versions and Postgres Versions and the compatibility.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list