Re: Upgrading Postgres question

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Tony Fernandez" <Tony(dot)Fernandez(at)vocalocity(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Upgrading Postgres question
Date: 2008-11-10 18:03:46
Message-ID: dcc563d10811101003l19e5eb9fg286f1c8ec9efd72f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 5, 2008 at 2:19 PM, Tony Fernandez
<Tony(dot)Fernandez(at)vocalocity(dot)com> wrote:
> Hello all,
>
>
>
> I am in the process of updating my DB on Postgres 8.1.11 to 8.3.4. I also
> use Slony 1.2.14 for replication.

Then you're set. One of the primary purposes of slony is upgrading in
place. Take one of your backup slaves offline, upgrade it to 8.3,
recreate it as a slony slave, and let it run for a few days. When all
seems well, swap the two servers. downtime measured in seconds.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2008-11-10 18:46:14 Current log files when rotating?
Previous Message Asko Oja 2008-11-10 16:48:09 Re: Logging in function with exception