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

On Mon, Sep 10, 2018 at 10:29:05PM +0530, kalyani kaniganti wrote:
> Hi Bruce,
> We have performed the same steps.
> But pg_ctl is throwing error as postmaster.pid is not found in old path and
> displays as is sever running ?
> pg_ctl status display output as server not running.
> May I know it's an bug in 9.4.19 .Any other suggestions ?

I suggest you show us exactly what you are doing and what you are
seeing. There is no known bug here yet.

---------------------------------------------------------------------------

> BR,
> Kalyani
>
>
> On Mon, Sep 10, 2018, 10:17 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> On Mon, Sep 10, 2018 at 12:14:43PM -0400, Bruce Momjian wrote:
> > On Mon, Sep 10, 2018 at 05:34:14PM +0530, kalyani kaniganti wrote:
> > > Hi Bruce,
> > >
> > > We have checked cluster status on both the server's data and we noticed
> source
> > > cluster state is in production and destination cluster state in
> shutdown.
> > > Database cluster state:               in production
> > > Database cluster state:               shut down
> > >
> > > How can we shut down the Database cluster?
> >
> > Uh, pg_ctl and point to the running data directory.
>
> Let me be more specific:
>
>         $ pg_ctl -D path-to-old-cluster stop
>
> e.g.,
>
>         $ pg_ctl -D /u/pg-old/data stop
>         waiting for server to shut down.... done
>         server stopped
>
> --
>   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 +
>

--
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 +