From: John Scalia <jayknowsunix@gmail.com>
To: Harshad Adalkonda <adalkondaharshad@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: pg_upgrade from V9.3.3 to V9.4.0
Date: Sat, 10 Jan 2015 11:22:41 -0500
Message-ID: <54B151D1.70304@gmail.com> (raw)
In-Reply-To: <CANnQH_gpdfb4gt+76gffvHYSon+UrQYCLaD89UP24zvigpU_SQ@mail.gmail.com>
References: <54B055C3.5070003@gmail.com>
<CANnQH_gpdfb4gt+76gffvHYSon+UrQYCLaD89UP24zvigpU_SQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Thanks Harshad,
I'll give this a try on Monday morning.
--
Jay
On 1/10/2015 8:43 AM, Harshad Adalkonda wrote:
>
> On Sat, Jan 10, 2015 at 3:57 AM, John Scalia <jayknowsunix@gmail.com <mailto:jayknowsunix@gmail.com>> wrote:
>
> Hi all,
>
> While we're not planning to migrate to the new version, I'm trying to gain some experience as the streaming replication has really changed in this version and indicates
> future directions for it. My environment is virtualized CentO/S 6.5, and this particular server is the current primary, not a standby. My problem is that the pg_upgrade is
> just hanging - for over an hour, before I killed it. I only see a "Verifying Cluster" message, and that's it. Even the 3 logs written by pg_upgrade, don't really tell me any
> more. Am I trying to go too far with this upgrade? Do I need to bring it V9.3.4 first, or what? The behavior just seems a bit odd. I've only run this prior going from 9.2.2
> to 9.3.3 and that had no issues.
> --
> Jay
>
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org <mailto:pgsql-admin@postgresql.org>)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
>
> Hi John Scalia,
>
> I have tried pg_upgrade from 9.3.3 to 9.4.0 and i have done with the following procedure which will solve your problem.
>
> Create .pgpass file in users home directory ~/.pgpass and add both server with their respective user & password
>
> Now Shut down 9.3.3 & 9.4.0 cluster
>
> Now when ever you run pg_upgrade utility the present working directory (pwd) should have write access of the current user e.g postgres
>
> First just check if clusters are Clusters are compatible with using -c options
>
> Example:
>
> /opt/PostgreSQL/9.4/bin/pg_upgrade -c -v -d /tmp/PostgreSQL/9.3.3/data/ -D /tmp/PostgreSQL/9.4.0/data/ -b /opt/PostgreSQL/9.3.3/bin/ -B /opt/PostgreSQL/9.4/bin/ -p 5888 -P 5999
> -U postgres
>
> If Result says Clusters are compatible then remove -c and start upgrading
>
> Example:
>
> /opt/PostgreSQL/9.4/bin/pg_upgrade -v -d /tmp/PostgreSQL/9.3.3/data/ -D /tmp/PostgreSQL/9.4.0/data/ -b /opt/PostgreSQL/9.3.3/bin/ -B /opt/PostgreSQL/9.4/bin/ -p 5888 -P 5999 -U
> postgres
>
> If Result says Upgrade Complete then your upgrade is completed successfully.
>
> I am also attaching the one file for reference.
>
> Hope this will resolve your problem.
>
> --
> Thanks & Regards,
> Harshad Adalkonda
> Database Administrator
> http://www.shreeyansh.com
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jayknowsunix@gmail.com, adalkondaharshad@gmail.com
Subject: Re: pg_upgrade from V9.3.3 to V9.4.0
In-Reply-To: <54B151D1.70304@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox