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

From DEGLAVE Remi
Subject RE: [PG_UPGRADE] 9.6 to 10.5
Date
Msg-id AM6PR02MB3782A1B25738FCE6513B55DFFE3E0@AM6PR02MB3782.eurprd02.prod.outlook.com
Whole thread Raw
In response to Re: [PG_UPGRADE] 9.6 to 10.5  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [PG_UPGRADE] 9.6 to 10.5
List pgsql-bugs
Hi,

Sorry for the response delay.
Thanks for your feedbacks, I'll try a 10.4 upgrade and then a minor upgrade to 10.5.

Thanks and regards,

Rémi DEGLAVE
Database Administrator
Lyreco
Phone: +33 (0)3 27 23 42 33
Rue du 19 Mars 1962 - 59770 MARLY - FRANCE 
http://www.lyreco.com

supporting the educational development of children throughout the world. 
Please, click here to discover Lyreco Actions for children.


-----Message d'origine-----
De : Bruce Momjian <bruce@momjian.us> 
Envoyé : mardi 14 août 2018 23:24
À : Martin Marques <martin.marques@2ndquadrant.com>
Cc : DEGLAVE Remi <remi.deglave@lyreco.com>; pgsql-bugs@postgresql.org; Michael Paquier <michael.paquier@gmail.com>
Objet : Re: [PG_UPGRADE] 9.6 to 10.5

On Fri, Aug 10, 2018 at 05:41:14PM -0300, Martin Marques wrote:
> El 10/08/18 a las 13:12, Bruce Momjian escribió:
> > 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":
> 
> He did mention trying to shutdown with different modes, and ended with 
> the same result after pg_upgrade.
> 
> I would recommend running pg_upgrade in verbose mode (add the -v 
> option to the cmd), capture the output and open a thread in 
> pgsql-general list (or send it back here for further review).

I have not seen any report from the original reporter so I have gone ahead and committed the fix suggested by Michael
Paquier.

This means that standby upgrades will fail in 10.5 until 10.6 is released.  Ugh!  I guess users can upgrade to 10.4 and
thendo a minor upgrade to 10.5 as a workaround.
 

-- 
  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 #15324: Non-deterministic behaviour from parallelised sub-query
Next
From: Martín Marqués
Date:
Subject: Re: [PG_UPGRADE] 9.6 to 10.5