Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42751=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1XHyqx-00037J-K6
 for pgsql-admin@arkaria.postgresql.org; Thu, 14 Aug 2014 17:30:19 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42751=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1XHyqw-0007hK-UE
 for pgsql-admin@arkaria.postgresql.org; Thu, 14 Aug 2014 17:30:18 +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 <jayknowsunix@gmail.com>)
 id 1XHyqw-0007gt-6S
 for pgsql-admin@postgresql.org; Thu, 14 Aug 2014 17:30:18 +0000
Received: from mail-yh0-x22b.google.com ([2607:f8b0:4002:c01::22b])
 by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1XHyqn-0000Lp-CN
 for pgsql-admin@postgresql.org; Thu, 14 Aug 2014 17:30:16 +0000
Received: by mail-yh0-f43.google.com with SMTP id 29so1314688yhl.30
 for <pgsql-admin@postgresql.org>; Thu, 14 Aug 2014 10:30:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=references:mime-version:in-reply-to:content-type
 :content-transfer-encoding:message-id:cc:from:subject:date:to;
 bh=m4woNZl2wrFmh9YiQsM6K34KIEg++JaOadPO1gghimk=;
 b=BPRwTXIemkfvQNYec8ilLT9wu5hjmvldu8OS19gR/inorFA4NG2uQf3MVuXQ+l1w28
 ZeUMnNVX5+VuYLwhZbZK6VFyOPIZmAPrWS2Yf6xIuMoev38yvA4ri1modp6h4PRR8Y4g
 ChBF8gr4K3LL+LEAoPad+UcSEOkaxFdlP+JDFxOVo4+vrYDwu7UheqkspTG2B9g0IDSh
 RlTd0IJuzVZzKT5yuQWC+xt9nFXNpj7zulPmAZbkLh3twpftszwQFF+xRvFrBTI/9Gws
 nhq/16cem8nCTrr1Qd/TOruk1K+GScLUe9MYMzFO/OlaYS4yKsxquEQa2etMaJcqAOfi
 L+AQ==
X-Received: by 10.236.98.40 with SMTP id u28mr19639770yhf.9.1408037406832;
 Thu, 14 Aug 2014 10:30:06 -0700 (PDT)
Received: from [192.168.254.1] (h77.89.102.166.static.ip.windstream.net.
 [166.102.89.77])
 by mx.google.com with ESMTPSA id q35sm11818562yhb.9.2014.08.14.10.30.05
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Thu, 14 Aug 2014 10:30:05 -0700 (PDT)
References: <53EBE4B6.5030904@gmail.com> <20140814024821.GB7858@momjian.us>
 <53ECB9E5.6000004@gmail.com> <20140814165755.GC7858@momjian.us>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20140814165755.GC7858@momjian.us>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5304C38-D3DF-4999-B1AC-5B688730F7DF@gmail.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
X-Mailer: iPad Mail (11D257)
From: jayknowsunix@gmail.com
Subject: Re: pg_upgrade hangs
Date: Thu, 14 Aug 2014 13:30:05 -0400
To: Bruce Momjian <bruce@momjian.us>
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Well, I'd pull the log for you, but the team has taken the VM offline and i=
s trying to replace it. I'll see when they get the new one built if any of =
this starts to repeat.

Sent from my iPad

> On Aug 14, 2014, at 12:57 PM, Bruce Momjian <bruce@momjian.us> wrote:
>=20
>> On Thu, Aug 14, 2014 at 09:30:13AM -0400, John Scalia wrote:
>> Well, it's now gotten much worse, and I really do not understand how
>> this is failing. I started off this morning trying to run pg_grade
>> with strace in the hope that I could find something hanging up, but
>> pg-upgrade is now failing and exiting very early. Almost immediately
>> after reporting "Checking cluster versions ok", it throws a SQL
>> command failed where it tried to create the temporary table
>> 'info_rels'. The error is that type "info_rels" already exists.
>>=20
>> My first thought was that a previous attempt had partially succeeded
>> and left some garbage in the new 9.3 instance. So, I deleted
>> everything in the 9.3 data directory and did a new initdb there, but
>> the problem continues to reoccur. I have since checked the old 9.2
>> database, including the template1 portion, but I don't see an
>> info_rels table in any of these. (I checked using "select * from
>> pg_tables;") I'd really like to know why it's failing here. Where is
>> it finding this info_rels table and why can't I find it? Is it
>> deleting it after it spits out this error? And is this table
>> something that gets repeatedly created and dropped during a
>> pg_upgrade?
>=20
> Well, you managed to show me nothing, so I can't really help you
> further.  info_rels is an internal C struture so I can't guess what is
> failing. I suggest you show the error, and read the message and then
> look in the log file it recommends, if any.
>=20
> --=20
>  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
>  EnterpriseDB                             http://enterprisedb.com
>=20
>  + Everyone has their own god. +


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin