Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tkmdf-0003zi-Gb for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Dec 2012 02:10:35 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Tkmde-00075U-My for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Dec 2012 02:10:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tkmdd-00075O-FG for pgsql-hackers@postgreSQL.org; Tue, 18 Dec 2012 02:10:33 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TkmdU-0002Gt-B5 for pgsql-hackers@postgreSQL.org; Tue, 18 Dec 2012 02:10:33 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1TkmdT-0003nt-0n; Mon, 17 Dec 2012 21:10:23 -0500 Date: Mon, 17 Dec 2012 21:10:23 -0500 From: Bruce Momjian To: Bernhard Schrader Cc: PostgreSQL-development Subject: Re: [ADMIN] Problems with enums after pg_upgrade Message-ID: <20121218021023.GC29143@momjian.us> References: <50CEFE95.9040301@innogames.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50CEFE95.9040301@innogames.de> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org 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. Can anyone suggest why enum upgrade is failing for this user? What should he be checking for? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers