Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Y9iGa-0007d5-Po for pgsql-admin@arkaria.postgresql.org; Fri, 09 Jan 2015 22:42:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Y9iGa-0005IJ-Ab for pgsql-admin@arkaria.postgresql.org; Fri, 09 Jan 2015 22:42:52 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Y9iGZ-0005ID-GV for pgsql-admin@postgresql.org; Fri, 09 Jan 2015 22:42:51 +0000 Received: from mail-yk0-x235.google.com ([2607:f8b0:4002:c07::235]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Y9iGS-00021r-97 for pgsql-admin@postgresql.org; Fri, 09 Jan 2015 22:42:49 +0000 Received: by mail-yk0-f181.google.com with SMTP id 142so5167996ykq.12 for ; Fri, 09 Jan 2015 14:42:43 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=q5+Vn6qbndi71XKTjwtfSotUBJk1vvV24ooPnzH6t90=; b=SBPjCLxpZ6vuE2ZH4A5ndvW/M2hFxDxhaoCTGa6xEgpLhA4ybyJ9zEMamS+L3SLKer /DBI6BAFZmwFj3YfR1ClhvLME2YshHiWzSl+M9pUr+QFHl9H5oDfV2WXyrSF6W4xl48V y49qfj253Iwef9yD9X7UrUyoqVH0exZg02KLAtLD2ajwMAUJUtXbILo5NnyXtP3nctln zF10BUx7hBhrf1BicZP9qWBB/e9A+K+QqRcui9kHtlWPE9pfTo1ENsfIiVxnPX3mte1N 1u79JDK+6i2XkCwnnf5hNJ9YSoHnU8XgDwDfQz6mnzXA9h+Ii0jXWeFU8wbzDXdWxzRI Aptw== X-Received: by 10.236.26.137 with SMTP id c9mr12844978yha.7.1420843363006; Fri, 09 Jan 2015 14:42:43 -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 d79sm5492029yha.24.2015.01.09.14.42.42 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Jan 2015 14:42:42 -0800 (PST) Message-ID: <54B0595A.4010309@gmail.com> Date: Fri, 09 Jan 2015 17:42:34 -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: Bruce Momjian CC: "pgsql-admin@postgresql.org" Subject: Re: pg_upgrade from V9.3.3 to V9.4.0 References: <54B055C3.5070003@gmail.com> <20150109223935.GA26822@momjian.us> In-Reply-To: <20150109223935.GA26822@momjian.us> Content-Type: text/plain; charset=windows-1252; 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 Thanks Bruce, I'll give that a try on Monday morning. -- Jay On 1/9/2015 5:39 PM, Bruce Momjian wrote: > On Fri, Jan 9, 2015 at 05:27:15PM -0500, 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. > I have never heard of a hang like that. I would try V9.3.4. > -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin