pg_upgrade 10.2

From: Murthy Nunna <mnunna(at)fnal(dot)gov>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: pg_upgrade 10.2
Date: 2018-06-12 20:34:56
Message-ID: DM5PR09MB15157D85EB291E8F7EA62E25B87F0@DM5PR09MB1515.namprd09.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general pgsql-performance

In older versions of pg_upgrade (e.g from 9.2 to 9.3), I was able to run pg_upgrade without stopping old cluster using the check flag.

pg_upgrade -b <old-bin> -B <new-bin> -d <old-data> -D <new-data> -p 5432 -P 5434 -r -v -k -c

Note the "c" flag at the end

However pg_upgrade in 10 (I tried from 9.3 to 10.4), when I did not stop the old cluster, the upgrade failed:

***
There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Failure, exiting

Is this expected?

Also, when I stopped the old cluster and ran pg_upgrade with "-c" flag, the file global/pg_control got renamed to global/pg_control.old. The "-c" flag never renamed anything in the old cluster in older pg_upgrade

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Adrian Klaver 2018-06-12 20:47:30 Re: pg_upgrade 10.2
Previous Message Heinemann, Manfred (IMS) 2018-06-12 20:15:38 RE: Segmentation fault with parallelism PG 10.4

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2018-06-12 20:47:30 Re: pg_upgrade 10.2
Previous Message Scott Stroupe 2018-06-12 20:07:09 Re: Print pg_lsn as a number?

Browse pgsql-performance by date

  From Date Subject
Next Message Adrian Klaver 2018-06-12 20:47:30 Re: pg_upgrade 10.2
Previous Message e-blokos 2018-06-07 09:40:39 Re: Client Server performance & UDS