On 4/26/07, Andrew Sullivan <[EMAIL PROTECTED]> wrote: > On Thu, Apr 26, 2007 at 02:33:25PM +0200, Paul Slootman wrote: > > - stop slony > > - install the new version > > of slony, I take it? Then yes.
Indeed :) > > - once the new server is in sync, stop the application updating the > > database, > > and switch the origin to the new server. > > Right. This is a switchover, and not a failover, note. Yep. > > Oh yeah, the versions of postgresql and slony I'm upgrading to is > > pretty much determined by the versions available in Debian. I built > > slony 1.0.5 myself back then, but I'd like to be able to use standard > > package versions from now on. > > Are you familiar with debuild? I think that at least in the case of > Slony, you're going to want to be able to build new packages fairly > easily, because it's still fairly young, and we've had some nasty > bugs turn up. Hmm, that sounds a bit worrying (the nasty bugs, that is)... Slony 1.0.5 has worked pretty well for me up to now, but now the application people are starting to ask for postgresql 8 as that should help performance, they say. I say they should fix their application, but do they listen.... :-) However, I see that there are packages of slony 1.2.9 available, although they're not in the just-released etch Debian version. That doesn't worry me too much though, at this stage that doesn't involve also upgrading half the other packages due to dependencies yet. And I'm a Debian developer myself, so the intricacies of Debian are familiar :-) Thanks, Paul Slootman _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
