Wed Jan 19 20:41:11 PST 2005
- Previous message: [Slony1-general] upgrading to new pg version
- Next message: [Slony1-general] Slony1 init script.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On January 19, 2005 12:18 pm, you wrote: > when you say promote nodes, you mean doing a slonik move set, right? > Because that's how i've reversed the role of master and slave in the > past when i need to do maintenance on the master db. I think maybe we > are talking about the same thing. lock set, wait for event, move set > change origin, wait for event. I'll just have to do this twice, once > to upgrade the slave and once to upgrade the master. and each time > i'll have to drop the slave, node, and bring it back up online and wait > for it to sync before performing the move set... Yes that is corect the way. > > unless there some other way of upgrading both the master and slave > without having to drop node/dump/init/reload/add node each one. I use the term promotion to describe the process of moving a subscriber to become an origan . > > --brian > > On Jan 19, 2005, at 12:36 PM, Darcy Buskermolen wrote: > > But at least with this methood you'll only experience 2, less than 20 > > second > > outage windows while you promote nodes... > > -------------------------------------------- > MobyGames > http://www.mobygames.com > The world's largest and most comprehensive? > gaming database project -- Darcy Buskermolen Wavefire Technologies Corp. ph: 250.717.0200 fx: 250.763.1759 http://www.wavefire.com
- Previous message: [Slony1-general] upgrading to new pg version
- Next message: [Slony1-general] Slony1 init script.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list