Re: PostgreSQL upgrade server A -> server B

From: Michael Glaesemann <grzm(at)seespotcode(dot)net>
To: "CAJ CAJ" <pguser(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL upgrade server A -> server B
Date: 2007-04-27 01:20:41
Message-ID: DF3949FB-5FFF-4BAB-86D5-7B4904A20EC2@seespotcode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message CAJ CAJ 2007-04-27 01:34:36 Re: PostgreSQL upgrade server A -> server B
Previous Message CAJ CAJ 2007-04-27 01:09:30 PostgreSQL upgrade server A -> server B