Tue Jun 17 09:05:14 PDT 2008
- Previous message: [Slony1-general] Upgrading from postgres 8.2.3 to 8.3.1
- Next message: [Slony1-general] Fixed a bug in wait for event
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Jun 17, 2008 at 3:05 AM, Martin Eriksson <m.eriksson at albourne.com> wrote: > Hi Salman, > > I just did this whole exercise with 1 master and 3 slaves and some of the > main points: > > * need two postgres installations running at the same time on > different ports 8.2.3, 8.3.1) > * I guess you will upgrade slony to 1.2.14 as well, as Christopher > pointed out need to do the "configure" and "make install" but if > you are upgrading your 8.2.3 slony installation as well, make sure > that you run "make clean" before doing the make install. else you > will get older lib files and you will get that error below (i got > it too) > * using MOVE_SET only switch the subscription of the nodes in > question, not other nodes that subscribe the original master, > those need to be switched manually with "Subscribe_set" > * If you like me, want to drop the 8.2.3 node and change the port of > the 8.3.1 to the old port of the 8.2.3. Take the dbs down change > the port in postgres.conf take the 8.3.1 db up on the new port > then for each node you need to issue the "store path" command to > upgrade the paths so all nodes know the correct new port. > > You can check my previous messages on this list as i went through most of > the problems you are likely to face doing this. > > Martin, Christopher, Thank you very much for the pointers. I successfully added the new slave and it is not syncing against the master. I'll search the list for Martin's replies to see what other problems can possibly arise.
- Previous message: [Slony1-general] Upgrading from postgres 8.2.3 to 8.3.1
- Next message: [Slony1-general] Fixed a bug in wait for event
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list