Re: [GENERAL] trouble with pg_upgrade 9.0 -> 9.1 - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [GENERAL] trouble with pg_upgrade 9.0 -> 9.1
Date
Msg-id 20121220114954.GH20015@momjian.us
Whole thread Raw
In response to Re: [GENERAL] trouble with pg_upgrade 9.0 -> 9.1  (Groshev Andrey <greenx@yandex.ru>)
List pgsql-hackers
On Thu, Dec 20, 2012 at 03:41:37PM +0400, Groshev Andrey wrote:
> > See that 786665369?  That is the pg_class.oid of the plob in the old
> > cluster, and hopefully the new one.  Find where the lob*_pkey index is
> > created and get that oid.  Those should match the same names of the
> > pg_class.oid in the old and new clusters, but it seems the new plob* oid
> > is matching the lob oid in the old cluster.
> >
> > Also, pg_upgrade sorts everything by oid, so it can't be that somehow
> > pg_upgrade isn't ordering things right, and because we already passed
> > the oid check, we already know they have the same oid, but different
> > names.
> >
> > --
> >   Bruce Momjian  <bruce@momjian.us>        http://momjian.us
> >   EnterpriseDB                             http://enterprisedb.com
> >
> >   + It's impossible for everything to be true. +
> 
> Yes, was the last question. How to find out which version should stay?
> And of course, I forgot to say a great big thank you!

You can pick either name to be the right one;  they just have to match. 
The oids are fine.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: ThisTimeLineID in checkpointer and bgwriter processes
Next
From: Simon Riggs
Date:
Subject: Re: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review]