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

On Wed, May 21, 2014 at 10:56:59AM -0600, Jeff Ross wrote:
>
> 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.

So the big question is why doesn't the existing 8.4 table have a toast
table? Did you use pg_upgrade on the old cluster before, e.g. from 8.3?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +