From: Bruce Momjian <bruce@momjian.us>
To: Guo, Yun <YGuo@cvent.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: pg_upgrade from 9.3 to 9.4 fails
Date: Mon, 5 Oct 2015 14:02:44 -0400
Message-ID: <20151005180244.GB6784@momjian.us> (raw)
In-Reply-To: <D2383215.484EC%yguo@cvent.com>
References: <D2381B50.48442%yguo@cvent.com>
<D2381B7B.48445%yguo@cvent.com>
<20151005172418.GA6784@momjian.us>
<D2383215.484EC%yguo@cvent.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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 = 1670699;
>
> This turns out to be empty in all of the databases:
> postgres=# SELECT * FROM pg_type WHERE oid = 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
> ---------+--------------+----------+--------+----------+---------+---------
> ----+----------------+--------------+----------+----------+----
> -----+----------+----------+-----------+------------+---------+----------+-
> ----------+------------+----------+------------+------------+--
> -----------+-----------+----------+--------------+---------------+---------
> ---+--------
> (0 rows)
OK, try running the error query in all the databases then.
> >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.
>
> If my old server system catalog is messed up is there way to repair it?
Usually, once we find the cause.
--
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 +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: bruce@momjian.us, YGuo@cvent.com
Subject: Re: pg_upgrade from 9.3 to 9.4 fails
In-Reply-To: <20151005180244.GB6784@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox