Re: BUG #15376: Postgres sql 9.4.19 pg_upgrade stops with error The source cluster was not shut down cleanly.

Hi Bruce,
Issue is solved after performing below steps

pgctl start -D <old data folder>
pgctl stop -D <old data folder>

But we tried to reinstall the postgressql and checked again. by default the
satndby cluster is going to in production state and while executing the
above commands sometimes the upgarde is working fine and issue is
inconsistent.

Do you have any suggestions.

BR,
Kalyani.k

On Tue, Sep 11, 2018, 8:04 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> On Tue, Sep 11, 2018 at 07:20:47AM +0530, kalyani kaniganti wrote:
> > Hi Bruce.
> >
> > Below commands are executed.
> >
> > pg_ctl -D <path to old data> stop
> >
> > output
> > pg_ctl: PID file "/tmp/folder/postgresql/postmaster.pid" does not exist
> > Is server running?
> >
> > pg_controldata <path to old data> output displayed as Database cluster
> : in
> > production
> >
> > pg_ctl status displays server not running
> >
> > We have performed same steps and executed this script with 9.4.17
> version of
> > postgreSQL and its working fine.
> > We can get the upgarded DB and we have compared the pg_control data in
> 9.4.17
> > version we can see the DB cluster status is in shut down state for NEW
> DB data
> > and OLD DB data.
> >
> > We are not understanding what has changed from 9.4.17 to 9.4.19.
>
> My guess is that Postgres was improperly shut down before you tried
> using pg_ctl stop. Of course, you didn't show me anything exact, so I
> can only guess.
>
> --
> 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 +
>