Fri Oct 10 11:20:48 PDT 2008
- Previous message: [Slony1-general] 1 BIG SYNC - 9million rows
- Next message: [Slony1-general] Using SLONY to Upgrade Postgres Versions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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..
- Previous message: [Slony1-general] 1 BIG SYNC - 9million rows
- Next message: [Slony1-general] Using SLONY to Upgrade Postgres Versions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list