Jim Archer wrote:

> --On Friday, September 23, 2005 5:44 PM -0400 Christopher Browne
> <cbbrowne at ca.afilias.info> wrote:
>
>> Listed below is a context diff for a patch which I intend to apply to
>> the 1.1 branch next week in order to generate a 1.1.1 release.
>
>
> Great news, thanks!
>
> That leads me to wonder, how does one go about upgrading Slony in a
> production environment?  Do we basically have to drop the Slony schema
> and rebuild all the nodes from scratch?
>  

Nope.  That would be very UnCool.

See <http://slony.info/>


      Upgrading

Beginning with version 1.0.5 the slon replication engine refuses to work
against any database that does not have the stored procedures for the
same version loaded or where the shared object containing the C language
support functions and the log trigger does not match the version number.

This means that the Slony installation on all nodes in a cluster must be
upgraded at once.

The proper upgrade procedure is this:

   1. Stop the slon replication engine on all nodes.
   2. Install the new Slony version on all nodes.
   3. Execute a slonik script containing the command

    update functions (id = );
    

      for every node in the cluster.
   4. Start all slon replication engines.


We've been careful to make sure that an upgrade adds tables and columns
as needed to the internal Slony-I tables