From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | "Zwettler Markus \(OIZ\)" <Markus(dot)Zwettler(at)zuerich(dot)ch>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade 9.6 to 12 without 9.6 binaries |
Date: | 2020-03-13 16:25:50 |
Message-ID: | 87zhck2pdd.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 3/13/20 6:47 AM, Zwettler Markus (OIZ) wrote:
>
>> We are running Postgres 9.6 on server A.
>>
>> We want to upgrade it to Postgres 12 on server B.
>>
>> pg_upgrade requires the old (-b) and new (-B) binary set on the same server.
>>
>> We don't want to install both binary sets on the same server as we
>> had some library conflicts in the past.
>>
>> Is there still a way to use pg_upgrade without the old (-b) binary
>> set (I am aware of pg_dump/pg_restore)?
>
> No. As I understand it pg_upgrade needs to see the state of old
> instance to recreate that state on the new instance.
True.
PgUpgrade will start/stop both versions separately perhaps a couple of
times as part of the workflow.
>
>>
>> Markus
>>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2020-03-13 17:36:39 | Re: vacuum full doubled database size |
Previous Message | Kevin Brannen | 2020-03-13 16:01:32 | RE: vacuum full doubled database size |