From: Scott Marlowe <scott.marlowe@gmail.com>
To: Knight, Doug <dknight@wsi.com>
Cc: Gauri Kanekar <meetgaurikanekar@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Installation Steps to migrate to Postgres 8.3.1
Date: Tue, 13 May 2008 08:37:59 -0600
Message-ID: <dcc563d10805130737h5dae8dfax51fd1799af9098d7@mail.gmail.com> (raw)
In-Reply-To: <8536F69C1FCC294B859D07B179F069440DC1B69F@EXCHANGE.ad.wsicorp.com>
References: <7e4ba9550805122240j7ed6a494hfc10a8b08dad073e@mail.gmail.com>
<dcc563d10805130125hcea33a1x39cd9f3ee81b0687@mail.gmail.com>
<8536F69C1FCC294B859D07B179F069440DC1B69F@EXCHANGE.ad.wsicorp.com>
On Tue, May 13, 2008 at 6:00 AM, Knight, Doug <dknight@wsi.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: scott.marlowe@gmail.com, dknight@wsi.com, meetgaurikanekar@gmail.com
Subject: Re: Installation Steps to migrate to Postgres 8.3.1
In-Reply-To: <dcc563d10805130737h5dae8dfax51fd1799af9098d7@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox