From: | "CAJ CAJ" <pguser(at)gmail(dot)com> |
---|---|
To: | "Michael Glaesemann" <grzm(at)seespotcode(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL upgrade server A -> server B |
Date: | 2007-04-27 01:34:36 |
Message-ID: | 467669b30704261834o5ad4c057ua903673d2aed2097@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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!
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos Moreno | 2007-04-27 01:58:53 | Feature Request --- was: PostgreSQL Performance Tuning |
Previous Message | Michael Glaesemann | 2007-04-27 01:20:41 | Re: PostgreSQL upgrade server A -> server B |