On 11-10-28 03:20 PM, Matthias Leopold wrote: > hi, You will have some issues that might make it easier to create a new slave replicate your db to that slave and then do a move master.
But you might be able to get around the issues. The things to keep in mind are: 1) You mentioned doing this for the master, that is important because in 1.2 you can't do a pg_dump of a slave. 2) See http://bugs.slony.info/bugzilla/show_bug.cgi?id=234 I do not know how this bug plays out (if at all) on a 1.2 install nor have I checked to see if advancing the xid rollover counter would work with 1.2 3) You will need to run UPDATE FUNCTIONS(...) after the upgrade to make sure slony uses 8.4 versions of stored procedures versus 8.3/8.1 versions. There also might be other issues I don't know about. > > i'm running a slony 1.2.21 cluster. the master postgres server has > postgres version 8.3.9 on i386 architecture. slave nodes mostly have > postgres 8.3.x, one has 8.4.x > > would it be possible to do the following: > > - stop write access to master server > > - stop all slons > > - pg_dump master database > > - shut old physical master server down > > - load the dump in a 8.4 postgres server with slony 1.2.21 on x86_64 > architecture with same network address as old physical master > > - start slons again > > - enable write access to new physical master and continue with replication > > ? > > thx for advice > matthias > > > _______________________________________________ > Slony1-general mailing list > [email protected] > http://lists.slony.info/mailman/listinfo/slony1-general _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
