Re: [PG_UPGRADE] 9.6 to 10.5 - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: [PG_UPGRADE] 9.6 to 10.5
Date
Msg-id 20180810161245.GA7815@momjian.us
Whole thread Raw
In response to [PG_UPGRADE] 9.6 to 10.5  (DEGLAVE Remi <remi.deglave@lyreco.com>)
Responses Re: [PG_UPGRADE] 9.6 to 10.5  (Michael Paquier <michael@paquier.xyz>)
Re: [PG_UPGRADE] 9.6 to 10.5  (Martin Marques <martin.marques@2ndquadrant.com>)
List pgsql-bugs
On Fri, Aug 10, 2018 at 12:51:29PM +0000, DEGLAVE Remi wrote:
> The source cluster was not shut down cleanly.
> 
> Failure, exiting
> 
>  
> 
> I tried to restart and shutdown clusters with another methods (-m options of
> pg_ctl, killing processes, …) still have the same issue.

There is new code in PG 10.5 thta detects that the server is cleanly
shut down.  You can no longer use '-m immediate' to shut down either
server, but 'smart' and 'fast' should be fine.  Can you run
pg_controldata on each cluster before you run pg_upgrade to verify that
they say "Shutdown":

    $ pg_controldata /u/pg/data
    ...
    Database cluster state:               shut down
                                          ---------

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +


pgsql-bugs by date:

Previous
From: Amit Kapila
Date:
Subject: Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid760676 when max_parallel_maintenance_workers > 0
Next
From: Peter Geoghegan
Date:
Subject: Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid760676 when max_parallel_maintenance_workers > 0