Re: Best practise for upgrade of 24GB+ database

From: Andreas Hasenack <panlinux(at)gmail(dot)com>
To: "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 17:21:25
Message-ID: CAKyYGbMoYELhmj=qXowPSM-05A20tKwrSb3mXM8iY4hGVO48gg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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?

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2012-01-23 18:12:53 Re: Best practise for upgrade of 24GB+ database
Previous Message Simon Riggs 2012-01-23 14:53:11 Re: two questions regarding warm-standby on 8.4