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

From CAJ CAJ
Subject Re: PostgreSQL upgrade server A -> server B
Date
Msg-id 467669b30704261834o5ad4c057ua903673d2aed2097@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL upgrade server A -> server B  (Michael Glaesemann <grzm@seespotcode.net>)
List pgsql-general

> 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.

Gee thanks... I guess i didn't RTFM!




pgsql-general by date:

Previous
From: Michael Glaesemann
Date:
Subject: Re: PostgreSQL upgrade server A -> server B
Next
From: "John D. Burger"
Date:
Subject: Re: DIfferent plans for explicit versus implicit join using link table