Received-SPF: pass (mail136-ch1: domain of innogames.de designates
	157.56.252.5 as permitted sender) client-ip=157.56.252.5;
	envelope-from=bernhrad.schrader@innogames.de;
	helo=DB3PRD0310HT004.eurprd03.prod.outlook.com ; .outlook.com ;
Message-ID: <50D02D13.3010004@innogames.de>
Date: Tue, 18 Dec 2012 09:45:07 +0100
From: Bernhard Schrader <bernhard.schrader@innogames.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Bruce Momjian <bruce@momjian.us>
CC: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: [ADMIN] Problems with enums after pg_upgrade
References: <50CEFE95.9040301@innogames.de>
 <20121218014137.GB29143@momjian.us>
In-Reply-To: <20121218014137.GB29143@momjian.us>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 12/18/2012 02:41 AM, Bruce Momjian wrote:
> On Mon, Dec 17, 2012 at 12:14:29PM +0100, Bernhard Schrader wrote:
>> Hello together,
>>
>> last thursday I upgraded one of our 9.0.6 postgresql servers to
>> 9.2.2 with pg_upgrade. So far everything seemed to work but we now
>> discover problems with the enum types. If we run one specific query
>> it breaks all time with such an error message:
>>
>> ERROR: invalid internal value for enum: 520251
>>
>> if this number should represent the enumtypid it is not existing
>> anymore in pg_enum.
>>
>> How could i solve this problem? should we regenerate all enums? or
>> what could we do?
>> Hopefully anyone has a clue, google doesn't seem to be the ressource
>> for this problem.
> We seriously tested the enum code so I am pretty confused why this is
> failing.  If you do pg_dump --binary-upgrade --schema-only, do you see
> that a number like this being defined just before the enum is added?
>
Hi Bruce,

if i am dumping this db and grepping through the dump, i can't find the=20
number.
As far as we can see, the enum that is affected has now the enumtypid 16728.

is there a table which keeps the possible typecasts from enum to=20
text/text to enum etc.? if so, maybe the mapping in here is corrupt=20
since the upgrade.

regards

--=20
Bernhard Schrader
System Administration

InnoGames GmbH
Harburger Schlo=DFstra=DFe 28 (Channel 4) - 21079 Hamburg - Germany
Tel +49 40 7889335-53
Fax +49 40 7889335-22

Managing Directors: Hendrik Klindworth, Eike Klindworth, Michael Zillmer
VAT-ID: DE264068907 Amtsgericht Hamburg, HRB 108973

http://www.innogames.com =96 bernhard.schrader@innogames.de


--=20
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers