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

From CAJ CAJ
Subject PostgreSQL upgrade server A -> server B
Date
Msg-id 467669b30704261809xb037cfckaffeb960b7cbebfd@mail.gmail.com
Whole thread Raw
Responses Re: PostgreSQL upgrade server A -> server B  (Michael Glaesemann <grzm@seespotcode.net>)
Re: PostgreSQL upgrade server A -> server Bx  (Oleg Bartunov <oleg@sai.msu.su>)
Re: PostgreSQL upgrade server A -> server B  (Hannes Dorbath <light@theendofthetunnel.de>)
List pgsql-general
Hello,

Forgive me if this has been discussed before (or if it sounds absurd)

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.

pg_dump on new server might look something like,
pg_dump <options> -h <old server> -h <new_server> dbname

or can it be used as-is by piping it?

pg_dump <options> -h <old server> dbname | pg_restore

Thanks!

pgsql-general by date:

Previous
From: Kenneth Downs
Date:
Subject: Re: plperl functions not re-entrant?
Next
From: Michael Glaesemann
Date:
Subject: Re: PostgreSQL upgrade server A -> server B