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-10 12:04:14 |
Message-ID: | CACAAi_5twp+su0AQ6xBD=drnFfd1VdxX5KGBsr8DBgH3XTaKig@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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?
BR
Kalyani.k
On Mon, Sep 10, 2018 at 3:45 PM kalyani kaniganti <kalyanithumati(at)gmail(dot)com>
wrote:
> HI Bruce,
>
> We are using below command for an upgrade and after executing the below
> command the status is returning with the cluster error.
> /opt/postgres/9.4/bin/pg_upgrade -b /usr/bin -B /opt/postgres/9.4/bin -d
> <old data path> -D <new data path>
> rc=$?
> Rc returns the mentioned error.
>
> When we check with pg_ctl status command output is showing as server not
> running.
>
> How can we check the database cluster is shut down using which command.Can
> you share us the details other than the pg_ctl.bR
> kalyani
>
>
>
>
> On Mon, Sep 10, 2018 at 9:40 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
>> On Mon, Sep 10, 2018 at 09:30:28AM +0530, kalyani kaniganti wrote:
>> > Hi Bruce,
>> > Thanks for the immediate reply.
>> > We are using pg_ctl command to shutdown the old server with no
>> option.In this
>> > case the pg_ctl will consider as smart shutdown if no option is
>> specified as
>> > per documentation .
>> > please find bellow command.
>> > <new path for data dir>/bin/pg_ctl -D <olddata dir path> stop
>>
>> Yes, this should be fine.
>>
>> > We are using the same script for multiple releases in Postgres sql to
>> upgrade
>> > the database from 9.1 to 9.4 .
>> > Same script is working fine in 9.4.17 version, while upgrading DB from
>> 9.1 to
>> > 9.4.17.
>>
>> OK.
>>
>> > From the release notes of 9.4.19 version we did not find any changes
>> done on
>> > pg_upgrade except one bug fix related to pg_upgrade has been fixed.
>> > Do we have to add in our code to check for graceful shutdown or we have
>> to wait
>> > for the next release?
>> > Please let us know if you have any workaround till the next minor patch
>> is
>> > released.
>>
>> Well, there is nothing pending in the next beta except a better error
>> message text. Can you show me the commands and the error you are
>> getting. The system is looking at the output from:
>>
>> $ pg_controldata $PGDATA
>>
>> The "Database cluster state:" must be "shut down" before running
>> pg_upgrade.
>>
>> --
>> 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 | Christoph Berg | 2018-09-10 13:33:09 | Re: [BUGS] BUG #13793: Please implement IP_FREEBIND option |
Previous Message | kalyani kaniganti | 2018-09-10 10:15:15 | Re: BUG #15376: Postgres sql 9.4.19 pg_upgrade stops with error The source cluster was not shut down cleanly. |