Re: Upgrading Database: need to dump and restore?

From: Bill Moran <wmoran(at)potentialtech(dot)com>
To: "Carlos Oliva" <carlos(at)pbsinet(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Upgrading Database: need to dump and restore?
Date: 2009-06-03 19:14:27
Message-ID: 20090603151427.3110ed27.wmoran@potentialtech.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

Basically, you can set up the new database server (using a different port
or whatever), and install/configure Slony. Slony will then keep your
two database in sync. Then you can switch over to the new database
whenever suits you:

http://www.slony.info

--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Grzegorz Jaśkiewicz 2009-06-03 19:14:46 Re: Upgrading Database: need to dump and restore?
Previous Message Geoffrey 2009-06-03 19:07:08 Re: warm standby with WAL shipping