Re: pg_upgrade fails: Mismatch of relation OID in database 8.4 -> 9.3 - Mailing list pgsql-hackers

From Jeff Ross
Subject Re: pg_upgrade fails: Mismatch of relation OID in database 8.4 -> 9.3
Date
Msg-id 537CDADB.5070509@commandprompt.com
Whole thread Raw
In response to pg_upgrade fails: Mismatch of relation OID in database 8.4 -> 9.3  (Jeff Ross <jeff@commandprompt.com>)
Responses Re: pg_upgrade fails: Mismatch of relation OID in database 8.4 -> 9.3  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 5/21/14, 9:13 AM, Bruce Momjian wrote:
>
> On Wed, May 21, 2014 at 09:11:05AM -0600, Jeff Ross wrote:
>> -- For binary upgrade, set heap's relfrozenxid
>> UPDATE pg_catalog.pg_class
>> SET relfrozenxid = '1944'
>> WHERE oid = 'contact_email'::pg_catalog.regclass;
>>
>> -- For binary upgrade, set toast's relfrozenxid
>> UPDATE pg_catalog.pg_class
>> SET relfrozenxid = '2715452'
>> WHERE oid = '22588';
>>
>>
>> I should run the update commands only, correct?
>
> Uh, not really. We need to replicate what pg_upgrade is doing, and I
> can't be sure I am replicating your environment if I try it here.
>
> You need to use 9.3 pg_dump to dump the schema on 8.4, then use that
> dump to recreate the table on 8.4 _and_ 9.3 and then check for toast
> existance.  You are not going to do a pg_dump on 9.3.
>


Thanks for the clarification.

Yes, using 9.3's pg_dump of 8.4 and applying it to both an 8.4 and a 9.3 
cluster, the contact_email table now has toast in both 8.4 and 9.3.

Jeff



pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Re: Bison 3.0 updates
Next
From: Tom Lane
Date:
Subject: Re: Bison 3.0 updates