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)? Thanks for the reply, its greatly appreciated! /kurt On Aug 29, 2007, at 3:25 PM, Brad Nicholson wrote: > On Wed, 2007-08-29 at 13:58 -0400, Kurt Overberg wrote: >> Do any detailed docs exist for creating a log shipping slony node? I >> am using postgresql8.0.4 and slony 1.1.5. I have so far done the >> following: > > Not sure about this case, but you really don't want to be using 1.1.5 > log shipping. There is a critical bug in the log shipping code in > that > release that will break your log shipped replica under normal > operation. > I'm not sure of the state of log shipping in the rest of the 1.1 > branch, > but I would high recommend the latest 1.2 release for log shipping, > there have been several other issues with it that have been fixed. > -- > Brad Nicholson 416-673-4106 > Database Administrator, Afilias Canada Corp. > Kurt Overberg [EMAIL PROTECTED] _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
