Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tl24b-0001RU-Qn for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Dec 2012 18:39:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Tl24a-0003A2-AE for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Dec 2012 18:39:24 +0000 Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tl24Z-00038C-5i for pgsql-hackers@postgresql.org; Tue, 18 Dec 2012 18:39:23 +0000 Received: from moutng.kundenserver.de ([212.227.17.10]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tl24V-0006Pf-0s for pgsql-hackers@postgresql.org; Tue, 18 Dec 2012 18:39:22 +0000 Received: from anarazel.de (p5DDC761D.dip.t-dialin.net [93.220.118.29]) by mrelayeu.kundenserver.de (node=mreu3) with ESMTP (Nemesis) id 0LvdiS-1T1oLZ0ubc-017XiS; Tue, 18 Dec 2012 19:39:17 +0100 Received: by anarazel.de (Postfix, from userid 1000) id 44FF51C0173; Tue, 18 Dec 2012 19:39:16 +0100 (CET) Date: Tue, 18 Dec 2012 19:39:16 +0100 From: Andres Freund To: Tom Lane Cc: Bernhard Schrader , Bruce Momjian , Andrew Dunstan , PostgreSQL-development Subject: Re: [ADMIN] Problems with enums after pg_upgrade Message-ID: <20121218183916.GA7666@awork2.anarazel.de> References: <50CEFE95.9040301@innogames.de> <20121218014137.GB29143@momjian.us> <50D02D13.3010004@innogames.de> <50D0914E.3040508@dunslane.net> <20121218162256.GA24700@momjian.us> <50D0B0AD.9010905@innogames.de> <11487.1355855052@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11487.1355855052@sss.pgh.pa.us> X-Provags-ID: V02:K0:HXofCv85JO0XZm2Twh005jIdsx03VEnl7It6j3/3uFG rAfhacfbcoTFXnQlSyke/Rl+eTZJlnyYdYeDos1E/fk5qD0z4T btntI+puBIOS7+ItOfPT0g7/wAKCuoZ8HWMnkWjaXP362tCJ3L 7CkTrA/Qulov0zOOmCUx1oxw/qvY96gN+NUOhwYujwf0UoPTXp XZsDxuwSI8YI75ttS8vxBGGpCj27KU02Fz023sHsaGjwAc9nRV LsmI4fRf6U616lSXncxLcoFRRjnlZFnJZh+VQ5Mr6xRdLxota/ cVekorytsPNjupLwB81H6QMd/5YbjjwAO29J2WmQYuBCr9/uHc S0CbwWuWDGkAm++TBHnCtSWr+h8/9V96rSi9GauUa 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 2012-12-18 13:24:12 -0500, Tom Lane wrote: > Bernhard Schrader writes: > > Beside of that, we tested a little bit more with the failing query: > > The statement which is causing the error is a big UPDATE-statement with > > FROM. After some testing we figured out that the subselect in the > > FROM-clause is working fine. And if we simplify the UPDATE-statement > > it's also working. We're able to show the data and we're able to do > > simple updates on the table. But the two things combined are not > > working. > > Does the table being updated have any indexes on enum columns? I'm > suspicious that the bogus OID is in an index page somewhere, and not > in the table at all. I already wondered whether it could be a problem caused by pg_upgrade not ignoring invalid indexes until recently, but I don't really see how it could cause an invalid oid to end up in the index. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers