From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres UPGRADE from 9.2 to 9.4 |
Date: | 2016-09-06 23:20:33 |
Message-ID: | CANu8FiwNijvAjafpFVGAM9F24F9mR3R52MzHA3NuzvsSS+HhPQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
If you use slony to replicate, you CAN have 9.2 on the master and 9.4 on
the slave.
On Tue, Sep 6, 2016 at 6:43 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 9/6/2016 3:27 PM, Rich Shepard wrote:
>
> On Wed, 7 Sep 2016, Patrick B wrote:
>
> 2 - I've never done a Postgres upgrade before, can you give some guide
> here? Is usually a easy thing? How long can it take? Is a downtime needed?
>
>
>
> I suggest the place to start is 'man pg_upgrade.' It is helpful.
>
>
> pg_upgrade would require both 9.2 (with your existing database directory)
> and 9.4 be installed on the same server.
>
> the easiest way to do this upgrade depends heavily on how large the
> database is. 'pg_dumpall -h oldserver | psql -h newserver' might be
> simplest for modest data sizes, but way too slow for larger data sets.
>
>
> --
> john r pierce, recycling bits in santa cruz
>
>
If you use slony to replicate, you CAN have 9.2 on the master and 9.4 on
the slave.
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2016-09-06 23:25:13 | Re: Postgres UPGRADE from 9.2 to 9.4 |
Previous Message | John R Pierce | 2016-09-06 22:43:52 | Re: Postgres UPGRADE from 9.2 to 9.4 |