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

From Michael Paquier
Subject Re: [PG_UPGRADE] 9.6 to 10.5
Date
Msg-id 20180810164240.GM13638@paquier.xyz
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
On Fri, Aug 10, 2018 at 12:12:45PM -0400, Bruce Momjian wrote:
> 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":

You are talking about 244142d, right?  I see this code bit:
+   if (strcmp(p, "shut down\n") != 0)
+   {
+       if (cluster == &old_cluster)
+           pg_fatal("The source cluster was not shut down cleanly.\n");
+       else
+           pg_fatal("The target cluster was not shut down cleanly.\n");
+   }

This seems incorrect for me in the case of standbys, as pg_controldata
reports in this case "shut down in recovery", and one can run pg_upgrade
on a standby as well, no?
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid760676 when max_parallel_maintenance_workers > 0
Next
From: Bruce Momjian
Date:
Subject: Re: [PG_UPGRADE] 9.6 to 10.5