Re: Installation Steps to migrate to Postgres 8.3.1

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Knight, Doug" <dknight(at)wsi(dot)com>
Cc: "Gauri Kanekar" <meetgaurikanekar(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Installation Steps to migrate to Postgres 8.3.1
Date: 2008-05-13 14:37:59
Message-ID: dcc563d10805130737h5dae8dfax51fd1799af9098d7@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, May 13, 2008 at 6:00 AM, Knight, Doug <dknight(at)wsi(dot)com> wrote:
> Hi,
> Along these lines, the usual upgrade path is a pg_dump/pg_restore set.
> However, what if your database is large (> 50GB), and you have to
> minimize your downtime (say less than an hour or two). Any suggestions
> on how to handle that kind of situation? It sure would be nice to have
> some kind of tool to update in-place a database, though I know that's
> not a likely path.

look up Slony

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Vivek Khera 2008-05-13 15:01:34 Re: RAID controllers for Postgresql on large setups
Previous Message Merlin Moncure 2008-05-13 12:07:22 Re: RAID controllers for Postgresql on large setups