From: | Martin Marques <martin(dot)marques(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us>, DEGLAVE Remi <remi(dot)deglave(at)lyreco(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: [PG_UPGRADE] 9.6 to 10.5 |
Date: | 2018-08-10 20:41:14 |
Message-ID: | 15fa3462-a3da-2134-1c4e-8127f50ed304@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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).
--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2018-08-10 23:33:55 | BUG #15321: XMLTABLE leaks memory like crazy |
Previous Message | Peter Geoghegan | 2018-08-10 20:15:47 | Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid 760676 when max_parallel_maintenance_workers > 0 |