Fri Jun 7 13:18:27 PDT 2013
- Previous message: [Slony1-general] Slony Versions and Postgres Versions and the compatibility.
- Next message: [Slony1-general] Slony 2.2.0 beta 4 released
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 06/06/13 04:16, Raghav wrote: > > __ > > 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." That is correct. Slony requires the same Slony version on all nodes, but supports running on top of different PostgreSQL version. Jan > > 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/ <http://raghavt.blogspot.com/> > > > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general > -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin
- Previous message: [Slony1-general] Slony Versions and Postgres Versions and the compatibility.
- Next message: [Slony1-general] Slony 2.2.0 beta 4 released
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list