| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | kalyanithumati(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15376: Postgres sql 9.4.19 pg_upgrade stops with error The source cluster was not shut down cleanly. |
| Date: | 2018-09-10 02:10:42 |
| Message-ID: | 20180910021042.GA22703@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Sep 9, 2018 at 06:22:24PM -0400, Bruce Momjian wrote:
> On Sun, Sep 9, 2018 at 04:14:45PM +0000, PG Bug reporting form wrote:
> What 9.4.19 fixed is that users were doing a pg_ctl -m immediate, and
> then running pg_upgrade, and getting _silently_ corrupted upgrades.
> 9.4.19 fixes this so pg_upgrade properly complains when this happens.
>
> You should only see that error if you are doing "immediate" shutdowns of
> your server, and this is not supported, and throws ane error. Are you
> seeing the pg_upgrade error message when you do a _clean_ shutdown of
> your servers?
Also, you can't run pg_upgrade directly on standby servers. You have to
either make it a primary server or use the rsync instructions in the
pg_upgrade docs. The next minor release will have a better error
message on this.
--
Bruce Momjian <bruce(at)momjian(dot)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 +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-09-10 03:38:22 | Re: BUG #15367: Crash in pg_fe_scram_free when using foreign tables |
| Previous Message | Bruce Momjian | 2018-09-09 22:22:24 | Re: BUG #15376: Postgres sql 9.4.19 pg_upgrade stops with error The source cluster was not shut down cleanly. |