From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
---|---|
To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
Cc: | Carlos Oliva <carlos(at)pbsinet(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Upgrading Database: need to dump and restore? |
Date: | 2009-06-03 19:17:59 |
Message-ID: | 2f4958ff0906031217h2a0bfe0t674f266d4397e9ba@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jun 3, 2009 at 8:14 PM, Bill Moran <wmoran(at)potentialtech(dot)com> wrote:
> In response to "Carlos Oliva" <carlos(at)pbsinet(dot)com>:
>
>> Woudl it be possible to keep the current postgresql version running in a
>> different port, install a new version of postgresql, and copy the data from
>> one version to the other while both versions are running? This might give
>> us time to copy the tables and databases one at a time and reconfigure the
>> database access for parts of the application until we complete the migration
>> to the new version.
>
> Your best bet would be to install Slony-I. One of the main design goals
> for Slony is to allow interruption-free upgrades.
I don't think it is "easy", but will do if you need to synchronize
data before switching.
--
GJ
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2009-06-03 19:26:17 | Re: warm standby with WAL shipping |
Previous Message | Grzegorz Jaśkiewicz | 2009-06-03 19:14:46 | Re: Upgrading Database: need to dump and restore? |