Thu Sep 9 06:34:19 PDT 2010
- Previous message: [Slony1-general] Upgrading slony
- Next message: [Slony1-general] Upgrading slony
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 9 Sep 2010, Ulas Albayrak wrote: > Hi, > > This might be a quite fundamental question, but the consequences of > being wrong could be dire so I'll ratghr be sure: I need to upgrade > Slony and the guide on the official Slony website says I should > terminate all slon processes then install the newer version of Slony. > My question is can I just build and install the newer version of Slony > parallel to the old and after running the "update functions"-script, > just delete the old slony files? The version you are upgrading from/too controls the answer to this question. Perhaps the docs are less clear then they should be. If you are upgrading from 1.2 to 2.0 you must uninstall slony with "uninstall node" on all nodes using the 1.2.x binaries then install the 2.0 binaries and then re-build (init cluster, store node, subscribe set etc...) your cluster. If your going from 2.0.3 to 2.0.4 or 1.2.x to 1.2.21 then you can use the update functions script. Two versions of slony can't normally be installed at the same time under the same postgresql server directory since the slony install scripts normally put files in $postgresqldir/lib and share that would conflict. In either case you should setup a test system with your old configuration and test your upgrade procedure. > > -- > Ulas Albayrak > ulas.albayrak at gmail.com > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general >
- Previous message: [Slony1-general] Upgrading slony
- Next message: [Slony1-general] Upgrading slony
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list