On Tue, Apr 3, 2012 at 2:09 PM, Robert Collins <[email protected]> wrote:
> Perhaps we can use slony to create a postgresql 9.1 instance on the > master server - there is space AFAICT - and then do one pivot to move > the master to that instance. That should be ~ the same downtime as > FDT, once the migration steps are tightened up. (We have to down > pgbouncer, sync the cluster, reconfigure it, reconfigure pgbouncer to > point to the new master, bring up pgbouncer, done). > > That would avoid running off of a slave (which I'm not entirely sure > is doable even with the excellent recent improvements), doesn't need > replication code changes (which are waste as we're dropping slony for > regular use anyhow) and has AFAICT the lowest downtime window. Yes, this has the lowest downtime window and has the advantage of us getting a freshly packed database and a better rollback story. -- Stuart Bishop <[email protected]> _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
