Re: pg_upgrade fails: Mismatch of relation OID in database 8.4 -> 9.3

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Jeff Ross <jeff(at)commandprompt(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade fails: Mismatch of relation OID in database 8.4 -> 9.3
Date: 2014-05-26 05:05:33
Message-ID: 20140526050533.GH18867@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2014-05-25 16:59:24 -0600, Jeff Ross wrote:
> Could a check like this be added to pg_upgrade?
> Is there a downside to
> adding a column big enough to force a toast table and then dropping it for
> any table that is too large not to have a toast table but doesn't?

It can take time and permanently 'uses up' a attribute number. So you'd
add costs for everyone for the few people that decided to do something
dangerous and unsupported...

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-05-26 05:09:16 Re: 9.4 btree index corruption
Previous Message Amit Kapila 2014-05-26 05:04:03 Re: relaying errors from background workers