From: "Guo, Yun" <YGuo@cvent.com>
To: Bruce Momjian <bruce@momjian.us>
CC: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: pg_upgrade from 9.3 to 9.4 fails
Thread-Topic: [ADMIN] pg_upgrade from 9.3 to 9.4 fails
Thread-Index: AQHQ/4mcAUs7p8odSEODO5MGegI4x55dIRKAgABIPQD//8cJgIAAQ7QA//+9XIA=
Date: Mon, 5 Oct 2015 18:04:13 +0000
Message-ID: <D23833AE.48502%yguo@cvent.com>
References: <D2381B50.48442%yguo@cvent.com> <D2381B7B.48445%yguo@cvent.com>
 <20151005172418.GA6784@momjian.us> <D2383215.484EC%yguo@cvent.com>
 <20151005180244.GB6784@momjian.us>
In-Reply-To: <20151005180244.GB6784@momjian.us>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.5.3.150624
Content-Type: text/plain; charset="us-ascii"
Content-ID: <515647C9B98215418DAF6E22529CAB1C@cvent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org


On 10/5/15, 2:02 PM, "Bruce Momjian" <bruce@momjian.us> wrote:

>On Mon, Oct  5, 2015 at 06:00:27PM +0000, Guo, Yun wrote:
>> >Wow, that is weird.  Can you run this query on the old cluster and show
>> >us the output?
>> >
>> >	SELECT * FROM pg_type WHERE oid =3D 1670699;
>>=20
>> This turns out to be empty in all of the databases:
>> postgres=3D# SELECT * FROM pg_type WHERE oid =3D 1670699;
>>  typname | typnamespace | typowner | typlen | typbyval | typtype |
>> typcategory | typispreferred | typisdefined | typdelim | typrelid | typ
>> elem | typarray | typinput | typoutput | typreceive | typsend |
>>typmodin |
>> typmodout | typanalyze | typalign | typstorage | typnotnull | t
>> ypbasetype | typtypmod | typndims | typcollation | typdefaultbin |
>> typdefault | typacl
>>=20
>>---------+--------------+----------+--------+----------+---------+-------
>>--
>> ----+----------------+--------------+----------+----------+----
>>=20
>>-----+----------+----------+-----------+------------+---------+----------
>>+-
>> ----------+------------+----------+------------+------------+--
>>=20
>>-----------+-----------+----------+--------------+---------------+-------
>>--
>> ---+--------
>> (0 rows)
>
>OK, try running the error query in all the databases then.

I tried it all databases. None of them has oid 1670699 in pg_type.

>
>> >This query doesn't even query pg_type, so it must be some internal use
>> >of pg_type.
>> >
>> >The reason check doesn't show the failure is that only a non-check run
>> >collects pg_class.oid values, but we never expect that to fail so we
>> >don't test it in check mode.
>> >
>> >My guess is that something is messed up in your system catalogs.  Can
>> >you try running this query in each old database and see if it fails.
>>=20
>> If my old server system catalog is messed up is there way to repair it?
>
>Usually, once we find the cause.
>
>--=20
>  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
>  EnterpriseDB                             http://enterprisedb.com
>
>+ As you are, so once was I. As I am, so you will be. +
>+ Roman grave inscription                             +


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