Skip site navigation (1) Skip section navigation (2)

Re: Best practise for upgrade of 24GB+ database

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Andreas Hasenack <panlinux(at)gmail(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Best practise for upgrade of 24GB+ database
Date: 2012-01-23 18:12:53
Message-ID: CAOR=d=0udSUXwjS0vxfOph3_+DRhvkeLfk+wKbgefsY1wm13eQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Mon, Jan 23, 2012 at 10:21 AM, Andreas Hasenack <panlinux(at)gmail(dot)com> wrote:
> On Fri, Jan 20, 2012 at 16:45, Nicholson, Brad (Toronto, ON, CA)
> <bnicholson(at)hp(dot)com> wrote:
>> In the past I've used Slony to upgrade much larger database clusters than yours with minimal down time (I'm talking seconds for the actual master switch).  You set up a new replica on the new version and then move the master from old to new.  No need to explicitly resync afterwards.
>
> Would that work to upgrade from, say, 8.4 to 9.1? Using slony?

It should.  As long as both can support the same version of slony
you're good to go.

In response to

pgsql-admin by date

Next:From: Gary WebsterDate: 2012-01-23 20:05:46
Subject: Re: two questions regarding warm-standby on 8.4
Previous:From: Andreas HasenackDate: 2012-01-23 17:21:25
Subject: Re: Best practise for upgrade of 24GB+ database

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group