From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
To: | CAJ CAJ <pguser(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL upgrade server A -> server Bx |
Date: | 2007-04-27 04:51:39 |
Message-ID: | Pine.LNX.4.64.0704270851090.12152@sn.sai.msu.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
see pg_migrator project which could help you.
Oleg
On Thu, 26 Apr 2007, CAJ CAJ wrote:
> 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!
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru)
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Childs | 2007-04-27 07:18:55 | Re: Business days |
Previous Message | John D. Burger | 2007-04-27 03:36:08 | Re: Processing a work queue |