You can just stop the slon processes, and drop the schema that holds  
the replication tables, then your all clean again.

-Kenny

On Oct 10, 2008, at 11:20 AM, kevin kempter wrote:

> Hi List;
>
> We're preparing to do an upgrade from 8.2.5 to 8.3.4 on a system  
> where we loose money if it's down - thus downtime is not an option.
>
> I plan to do this:
>
>
> 1) setup a new 8.3.x cluster.
> 2) install SLONY on the old 8.2 cluster and the new 8.3.x cluster
> 3) Create/setup a SLONY replication set between the  two clusters  
> (the old 8.2 cluster/db as the master and the 8.3.x cluster as the  
> slave)
> 4) Initialize/start replication
> 5) Wait for replication to complete
> 6) Modify / create a 'switchover' script that also moves the  
> connections (via an I.P. alias)
> 7) execute a switchover
>
> My question is this:
>
> Once I get to this point we want to remove SLONY completely, while  
> leaving the new 8.3.4 master in place as the only server in read/ 
> write mode.
>
> Do I execute a drop node ? If so, can I execute a drop node on the  
> master ?
> Or is there a better approach ?
>
> Thanks in advance..
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general