Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Y9i1k-00071o-TT for pgsql-admin@arkaria.postgresql.org; Fri, 09 Jan 2015 22:27:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Y9i1k-00011i-4x for pgsql-admin@arkaria.postgresql.org; Fri, 09 Jan 2015 22:27:32 +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 1Y9i1j-00011c-7y for pgsql-admin@postgresql.org; Fri, 09 Jan 2015 22:27:31 +0000 Received: from mail-yh0-x22a.google.com ([2607:f8b0:4002:c01::22a]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Y9i1f-0008Ln-KV for pgsql-admin@postgresql.org; Fri, 09 Jan 2015 22:27:30 +0000 Received: by mail-yh0-f42.google.com with SMTP id v1so5364996yhn.1 for ; Fri, 09 Jan 2015 14:27:24 -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 :content-type:content-transfer-encoding; bh=M3o1cFlgHEc+56WAu24iugvsF78/QdedjTO+mJ+P5tE=; b=cpZB9UTM6a+K5Ly2aOI7wM5g6jYLyKxMcHnwfUlw3b/l3CxZe8cYGZDEe2oCcEQrUU MaKjQgwJlnPw3qugjcQVHdAIQwatDnfjdR6QQLa5X7GbbQbvEkIQhroBWBmtjpkTPsF5 TlYkkzi4AdkPZSPlzJciy6Bcz8pwc45dJ9mNzEjM0JSeTfLOCBQCu23F7/ld+4uohCZN kv6sYZviGW2aVRHBeVv6APoBC8QGPzIATVvG1vwCWW6EjMYzoeZOCQLXWUSVfR5Gbk95 ZfD0jn9kUpIVFPYFg+hSBp/i7IV31M3khPGHW+v3fKBw5NbK2jlijjhI8EiTtAuTfe9z g1EA== X-Received: by 10.236.26.143 with SMTP id c15mr13206434yha.192.1420842444064; Fri, 09 Jan 2015 14:27:24 -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 o47sm2784216yhd.48.2015.01.09.14.27.23 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Jan 2015 14:27:23 -0800 (PST) Message-ID: <54B055C3.5070003@gmail.com> Date: Fri, 09 Jan 2015 17:27:15 -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: "pgsql-admin@postgresql.org" Subject: pg_upgrade from V9.3.3 to V9.4.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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 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