Re: PostgreSQL upgrade server A -> server B - Mailing list pgsql-general

From Michael Glaesemann
Subject Re: PostgreSQL upgrade server A -> server B
Date
Msg-id DF3949FB-5FFF-4BAB-86D5-7B4904A20EC2@seespotcode.net
Whole thread Raw
In response to PostgreSQL upgrade server A -> server B  ("CAJ CAJ" <pguser@gmail.com>)
Responses Re: PostgreSQL upgrade server A -> server B  ("CAJ CAJ" <pguser@gmail.com>)
List pgsql-general
On Apr 26, 2007, at 20:09 , CAJ CAJ wrote:

> Upgrading large postgres databases (100GB+) takes awfully long time
> when doing dump/restore. I was wondering if this process can be
> optimized by directly dumping to a new version of Pg database
> directly on another server without having to dump to the filesystem
> and then restore it.

 From the fine documentation in the section entitled "Migration
Between Releases"

http://www.postgresql.org/docs/8.2/interactive/migration.html

> The least downtime can be achieved by installing the new server in
> a different directory and running both the old and the new servers
> in parallel, on different ports. Then you can use something like
>
> pg_dumpall -p 5432 | psql -d postgres -p 6543
>
> to transfer your data.

Hope that helps.

Michael Glaesemann
grzm seespotcode net



pgsql-general by date:

Previous
From: "CAJ CAJ"
Date:
Subject: PostgreSQL upgrade server A -> server B
Next
From: "CAJ CAJ"
Date:
Subject: Re: PostgreSQL upgrade server A -> server B