Re: Upgrading databases

I didn't actually run Sloany, so their may be some better people to ask.
 
However, the versions of Sloany depend on different versions of postgres - so if you use the latest version of Postgres, then you'll need the latest version of Sloany.  From what I could tell, you run Sloany on your master (which ever database you want to propogate - probably an old database) and it updates/populates the slaves (the new database).  So you'll have to get an older version os Sloany to do this.  Again, I never ran it so take my advice for what it's worth.


--- On Sat, 11/14/09, Greg Stark <[email protected]> wrote:


From: Greg Stark <[email protected]>
Subject: Re: Upgrading databases
To: "Greg Sabino Mullane" <[email protected]>
Cc: [email protected], [email protected]
Date: Saturday, November 14, 2009, 11:48 AM


On Sat, Nov 14, 2009 at 3:28 PM, Greg Sabino Mullane <[email protected]> wrote:
> 3. Slony. Setup a slave database, get everything in sync, then switch over to the
> new database. Very minimal downtime (seconds to minutes). Requires all tables
> have primary keys.
>
> 4. Bucardo. Similar to the steps of Slony above. More forgiving of interruptions
> in the original replication event.

I've never done this process myself. I'm wondering how flexible Slony
and Bucardo are with the versions of Postgres they support.

Does the Slony version run on the new version have to match the Slony
version on the old one? Do old versions of Slony work on new versions
of Postgres? Or do you have to update the version of Slony on the old
database before you can move to a new database version because the new
database version requires a newer version of Slony?

I'm even less familiar with Bucardo but have the same questions there too.


-- 
greg