Skip site navigation (1) Skip section navigation (2)

Re: pg_upgrade relation OID mismatches

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade relation OID mismatches
Date: 2011-11-22 20:42:35
Message-ID: 201111222042.pAMKgZv08051@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter Eisentraut wrote:
> I thought these were fixed a while ago, but I'm still seeing these when
> upgrading from master to self (using testing script sent in a while
> ago).   This is completely reproducible.  What's happening?
> 
> ...
> Restoring user relation files
>   /home/peter/devel/postgresql/git/postgresql/contrib/pg_upgra
> Mismatch of relation OID in database "regression": old OID 16701, new OID 16689
> Failure, exiting

Yes, I certainly thought they were all addressed.  What object is 16701
in the old database?  Anything unusual about it?  This is saying the
relation oid was not preserved.

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

  + It's impossible for everything to be true. +

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2011-11-22 21:17:20
Subject: Re: Review for "Add permission check on SELECT INTO"
Previous:From: Simon RiggsDate: 2011-11-22 20:23:34
Subject: Not HOT enough

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group