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

From Evan D. Hoffman
Subject Re: Re: [GENERAL] pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4
Date
Msg-id CABRB-LsHGXM_XuwjHv8TQwPdRXfRm2tY58q63aGK1Ggvg+gdkw@mail.gmail.com
Whole thread Raw
In response to Re: Re: [GENERAL] pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Re: [GENERAL] pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
<div dir="ltr">Adding & dropping a column resolved the problem.  Currently vacuuming the new cluster.  Thanks for
yourhelp everybody!</div><div class="gmail_extra"><br /><br /><div class="gmail_quote">On Sat, May 11, 2013 at 4:58 PM,
BruceMomjian <span dir="ltr"><<a href="mailto:bruce@momjian.us" target="_blank">bruce@momjian.us</a>></span>
wrote:<br/><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div
class="im">OnFri, May 10, 2013 at 08:03:38PM -0400, Bruce Momjian wrote:<br /> > On Fri, May 10, 2013 at 12:36:21PM
-0400,Evan D. Hoffman wrote:<br /> > >     "........pg.dropped.16........" INTEGER /* dummy */,<br /> > >  
 "........pg.dropped.17........" INTEGER /* dummy */,<br /> > >     "........pg.dropped.18........" INTEGER /*
dummy*/,<br /> > >     "........pg.dropped.19........" INTEGER /* dummy */,<br /> > >    
"........pg.dropped.20........"INTEGER /* dummy */,<br /> > >     "........pg.dropped.21........" INTEGER /*
dummy*/,<br /> > >     "........pg.dropped.22........" INTEGER /* dummy */,<br /> > >    
"........pg.dropped.23........"INTEGER /* dummy */,<br /> > >     "........pg.dropped.24........" INTEGER /*
dummy*/,<br /> > >     "........pg.dropped.25........" INTEGER /* dummy */,<br /> > >    
"........pg.dropped.26........"INTEGER /* dummy */,<br /> > >     ha27 character varying(10) DEFAULT
'UNKNOWN'::charactervarying,<br /> > >     "........pg.dropped.28........" INTEGER /* dummy */,<br /> > >  
 dr29 character varying(10)<br /> ><br /> > OK, this verifies that the table had a lot of DDL churn.  I have no
idea<br/> > how to pursue this further because I am unsure how we are going to<br /> > replicate the operations
performedon this table in the past, as you<br /> > mentioned much of this was before your time on the job.<br />
><br/> > Evan, I suggest you force a toast table on the table by doing:<br /> ><br /> >       ALTER TABLE
bpm.setupinfoADD COLUMN dummy TEXT;<br /> ><br /> > Then drop the column.  That will create a toast table and
willallow<br /> > pg_upgrade to succeed.<br /><br /></div>FYI, I did test adding a TEXT column and altering a column
toTEXT on<br /> Postgres 9.1, and both created a toast table.  I am still have no clues<br /> about what would have
causedthe missing toast table.<br /><div class="HOEnZb"><div class="h5"><br /> --<br />   Bruce Momjian  <<a
href="mailto:bruce@momjian.us">bruce@momjian.us</a>>       <a href="http://momjian.us"
target="_blank">http://momjian.us</a><br/>   EnterpriseDB                             <a href="http://enterprisedb.com"
target="_blank">http://enterprisedb.com</a><br/><br />   + It's impossible for everything to be true. +<br
/></div></div></blockquote></div><br/></div> 

pgsql-hackers by date:

Previous
From: amul sul
Date:
Subject: Re: psql connection reset failed
Next
From: Amit Kapila
Date:
Subject: Re: Fast promotion failure