Re: pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4

From: Igor Neyman <ineyman(at)perceptron(dot)com>
To: "Evan D(dot) Hoffman" <evandhoffman(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4
Date: 2013-05-08 20:31:51
Message-ID: A76B25F2823E954C9E45E32FA49D70EC1B7CDA81@mail.corp.perceptron.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> -----Original Message-----
> From: Evan D. Hoffman [mailto:evandhoffman(at)gmail(dot)com]
> Sent: Wednesday, May 08, 2013 4:22 PM
> To: Igor Neyman
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] pg_upgrade fails, "mismatch of relation OID" -
> 9.1.9 to 9.2.4
>
> Well, each time it fails it refers to the file
> "/var/lib/pgsql/9.1/data/base/16406/3016054", but that's not the file
> associated with OID 2938685.
>
> Here's the output of that query:
>
> db=# Select relname from pg_class where relfilenode = 3016054::oid;
> relname
> ---------
> (0 rows)
>
> db=#
>
>

And that is before running pg_upgrade, right?

Seems like some kind of pg_catalog corruption.
I guess, Bruce Momjian would know better, what's going on here.

Igor Neyman

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gavin Flower 2013-05-08 21:03:20 Re: Does it make sense to break a large query into separate functions?
Previous Message Tom Lane 2013-05-08 20:30:26 Re: pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4

Browse pgsql-hackers by date

  From Date Subject
Next Message Ray Stell 2013-05-08 21:05:05 pg_upgrade -u
Previous Message Tom Lane 2013-05-08 20:30:26 Re: pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4