On Wed, 2007-08-29 at 20:23 -0400, Kurt Overberg wrote: > Brad, > > Thanks for the warning about log shipping on 1.1.5. I actually think > I ran across that bug soon after my post (my subscriber fell > waaaaaaay behind) :-) > > I'd like to upgrade, but this is a heavily used production cluster > that I somehow managed to cobble together and keep working (I'm > nowhere near a slony/pg expert, I'm just persistent), so I'm a little > nervous about upgrading slony across the entire thing (1 master, 3 > subscriber nodes). The upgrade process seems deceptively simple > (compile new slony, get the libs into postgresql, then run update > functions), but is it really that simple? Should I not be nervous > and plow ahead? How easy is it to find a consultant who knows how to > do this stuff (confidently)?
It is that simple, however you should be somewhat nervous and test it all out first. You'll likely want an outage during the upgrade. If not, you should at least force all connections to you database to be reset after the upgrade or you may hit some problems. I think you are either going have to forget about log shipping, or do the upgrade. -- Brad Nicholson 416-673-4106 Database Administrator, Afilias Canada Corp. _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
