From: | kalyani kaniganti <kalyanithumati(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | 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-11 01:50:47 |
Message-ID: | CACAAi_4hHwkpjC4Qavsx3MpVEBDD_4=sDddnSRD681U2Y=5Lzg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.
BR
Kalyani
On Mon, Sep 10, 2018 at 11:18 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> 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 +
>
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2018-09-11 02:09:26 | BUG #15378: SP-GIST memory context screwup? |
Previous Message | Bruce Momjian | 2018-09-10 17:48:23 | Re: BUG #15376: Postgres sql 9.4.19 pg_upgrade stops with error The source cluster was not shut down cleanly. |