Re: Upgrade Failure

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Upgrade Failure
Date: 2023-07-18 14:44:03
Message-ID: 7bd4204a-ba57-2c12-1dcd-073a1470eb6c@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

pg_ctl is not pg_controldata.

(I bet you ran "pg_ctl stop --mode=immediate".  That's not a clean shutdown.)

On 7/18/23 05:26, Johnathan Tiamoh wrote:
> I used pg_ctl to stop the cluster.
>
> When I used the same pg_ctl to check status, it says no server is running
>
> On Tue, Jul 18, 2023 at 6:14 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> > On 18 Jul 2023, at 12:02, Johnathan Tiamoh
> <johnathantiamoh(at)gmail(dot)com> wrote:
>
> > The source cluster was not shut down cleanly.
> > Failure, exiting
> >
> > Please how do you resolve this
>
> pg_upgrade runs bin/pg_controldata on the source cluster data
> directory and
> ensures that the "Database cluster state" says "shut down". If you run the
> same command, which state is the cluster reported to be in?
>
> --
> Daniel Gustafsson
>

--
Born in Arizona, moved to Babylonia.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Devin Ivy 2023-07-18 17:58:27 Effects of dropping a large table
Previous Message David Rowley 2023-07-18 11:34:39 Re: Query take a long time and use no index