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

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: "Evan D(dot) Hoffman" <evandhoffman(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Igor Neyman <ineyman(at)perceptron(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [GENERAL] pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4
Date: 2013-05-13 16:56:03
Message-ID: 87ehdarf8c.fsf@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:

> On Fri, May 10, 2013 at 08:03:38PM -0400, Bruce Momjian wrote:
>
>> On Fri, May 10, 2013 at 12:36:21PM -0400, Evan D. Hoffman wrote:
>> > "........pg.dropped.16........" INTEGER /* dummy */,
>> > "........pg.dropped.17........" INTEGER /* dummy */,
>> > "........pg.dropped.18........" INTEGER /* dummy */,
>> > "........pg.dropped.19........" INTEGER /* dummy */,
>> > "........pg.dropped.20........" INTEGER /* dummy */,
>> > "........pg.dropped.21........" INTEGER /* dummy */,
>> > "........pg.dropped.22........" INTEGER /* dummy */,
>> > "........pg.dropped.23........" INTEGER /* dummy */,
>> > "........pg.dropped.24........" INTEGER /* dummy */,
>> > "........pg.dropped.25........" INTEGER /* dummy */,
>> > "........pg.dropped.26........" INTEGER /* dummy */,
>> > ha27 character varying(10) DEFAULT 'UNKNOWN'::character varying,
>> > "........pg.dropped.28........" INTEGER /* dummy */,
>> > dr29 character varying(10)
>>
>> OK, this verifies that the table had a lot of DDL churn. I have no idea
>> how to pursue this further because I am unsure how we are going to
>> replicate the operations performed on this table in the past, as you
>> mentioned much of this was before your time on the job.
>>
>> Evan, I suggest you force a toast table on the table by doing:
>>
>> ALTER TABLE bpm.setupinfo ADD COLUMN dummy TEXT;
>>
>> Then drop the column. That will create a toast table and will allow
>> pg_upgrade to succeed.
>
> FYI, I did test adding a TEXT column and altering a column to TEXT on
> Postgres 9.1, and both created a toast table. I am still have no clues
> about what would have caused the missing toast table.

Possibly manual catalog updates to change a varchar(N) to text and
whoopsie! That may be one explanation.

> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + It's impossible for everything to be true. +
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Sahagian, David 2013-05-13 18:23:22 replanning Prepared Statements ?
Previous Message Vincent Veyron 2013-05-13 16:13:08 Re: refactoring a database owner without "reassign owned"

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-05-13 16:59:47 Re: erroneous restore into pg_catalog schema
Previous Message Tom Lane 2013-05-13 16:35:13 Re: erroneous restore into pg_catalog schema