Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Y9yof-0002M2-3h for pgsql-admin@arkaria.postgresql.org; Sat, 10 Jan 2015 16:23:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Y9yod-0002VY-9I for pgsql-admin@arkaria.postgresql.org; Sat, 10 Jan 2015 16:23:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Y9yob-0002Ub-Rp for pgsql-admin@postgresql.org; Sat, 10 Jan 2015 16:23:06 +0000 Received: from mail-yh0-x22d.google.com ([2607:f8b0:4002:c01::22d]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Y9yoS-0002db-ML for pgsql-admin@postgresql.org; Sat, 10 Jan 2015 16:23:04 +0000 Received: by mail-yh0-f45.google.com with SMTP id f10so6581255yha.4 for ; Sat, 10 Jan 2015 08:22:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=IEzqDkCUwlINSPMCMU6uyxOVRm09dqctb7Lg0zv0I5c=; b=XSPQILCtS8qv2VGJ24VREA+jfV+qSBPo4AJ2ZgD/NvmqulNfyYatALu1xk9TBbvVmu 3iQFsceg8ngDLuhKX7GzSYynzYHsrUmjP3gzUrUcINQ55aY94xq6MdTidwWK+R8MZC+L 3/Puuv+jmhCwt41W7qUPjySIb0vFe09OdBUJ+Mdcv2JOpiwdjBFf4hlXBAKnGO/SEz/M PrSty9UxZQ+1q5c5KMMdb6MbT4fbayYwlCnxCfxeu3G1S1E+NUu4crAUVO+NpnPvfMQH 3yhBVCmaVUyBCjGRv3wLMs4PvdFJFR1GDyWZCaHCGmsrIbztO2KezB/xVR4/Va+GWLGH q/xA== X-Received: by 10.170.220.195 with SMTP id m186mr18675370ykf.58.1420906973405; Sat, 10 Jan 2015 08:22:53 -0800 (PST) Received: from [192.168.254.2] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id c63sm1607599yho.9.2015.01.10.08.22.52 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Jan 2015 08:22:52 -0800 (PST) Message-ID: <54B151D1.70304@gmail.com> Date: Sat, 10 Jan 2015 11:22:41 -0500 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Harshad Adalkonda , "pgsql-admin@postgresql.org" Subject: Re: pg_upgrade from V9.3.3 to V9.4.0 References: <54B055C3.5070003@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------070009030709080208070001" X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org This is a multi-part message in MIME format. --------------070009030709080208070001 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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 > 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 ) > 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 > --------------070009030709080208070001 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit 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> 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)
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


--------------070009030709080208070001--