From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Move cluster to new host, upgraded version |
Date: | 2018-11-11 20:22:51 |
Message-ID: | 38cdd93b-e0be-ca3b-decd-64072356e6ce@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/11/18 12:18 PM, Rich Shepard wrote:
> On Sun, 11 Nov 2018, Andrew Gierth wrote:
>
>> The most reliable and preferred procedure is to use the _new_ version's
>> pg_dumpall, for example by allowing access to the old host from the new
>> one (possibly using an ssh port forward), or (on OSes that make it
>> easy to
>> do package installs of multiple versions) to install the new pg_dump and
>> pg_dumpall on the old system.
>
> Andrew,
>
> Using the SlackBuilds.org script with an updated version number
> worked for
> 11.1. So, I'll install it on the old desktop and upgrade in place. Then I
> can use the 11.1 pg_dumpall on the data directory and copy that over to the
> new desktop.
pg_dumpall is going to need to run against a Postgres server not just a
data directory. If both your old and new machines are on the same
network, why not just point the 11.1 pg_dumpall(on the new machine) at
the 9.5 server running on the old machine?
>
> Thanks,
>
> Rich
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2018-11-11 20:51:15 | Re: Move cluster to new host, upgraded version |
Previous Message | Rich Shepard | 2018-11-11 20:18:19 | Re: Move cluster to new host, upgraded version |