On 4/18/07, Bill Moran <wmoran at collaborativefusion.com> wrote:
>
>
> Based on the docs here:
> http://slony.info/documentation/slonyupgrade.html
> it would seem that I have to run the exact same version of Slony on all
> nodes at all times.  If I want to change that version, I have to update
> all nodes simultaneously.
>
> With regards to updating and versions, is this for _any_ version change?
> I'm guessing that I can't have a cluster with some 1.1 Slony and some 1.2
> Slony.
>
> But, in this particular case, I'm looking at moving some systems from
> 1.2.6
> to 1.2.9.  Do I have to move them all at once, or is the API locked down
> in the 1.2 version so that slight disparities are OK?


This might be a good design goal for slony 2.0: inter-database compatibility
between different revisions of the same major.minor version. It'd be a nice
analogue to the idea of not requiring an initdb across major.minor versions
of PostgreSQL. While it wouldn't let you avoid taking an outage (well,
exclusive locks across all tables in all sets) to upgrade functions, it
would let you stagger the upgrades across the cluster. I doubt it's worth
the extra maintenance effort though.

Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070418/=
1909b35c/attachment.htm