Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tl4ao-0003oX-AH for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Dec 2012 21:20:50 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Tl4an-0006Gj-R7 for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Dec 2012 21:20:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tl4am-0006GL-OY for pgsql-hackers@postgresql.org; Tue, 18 Dec 2012 21:20:48 +0000 Received: from ch1ehsobe002.messaging.microsoft.com ([216.32.181.182] helo=ch1outboundpool.messaging.microsoft.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tl4ah-0002mX-T3 for pgsql-hackers@postgresql.org; Tue, 18 Dec 2012 21:20:48 +0000 Received: from mail127-ch1-R.bigfish.com (10.43.68.252) by CH1EHSOBE002.bigfish.com (10.43.70.52) with Microsoft SMTP Server id 14.1.225.23; Tue, 18 Dec 2012 21:20:39 +0000 Received: from mail127-ch1 (localhost [127.0.0.1]) by mail127-ch1-R.bigfish.com (Postfix) with ESMTP id 5E1192202DD; Tue, 18 Dec 2012 21:20:39 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.252.5; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0310HT005.eurprd03.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -4 X-BigFish: PS-4(zzbb2dI98dI9371Ic89bh1432Izz1d74h1de0h1d18h1202h1e76h1d1ah1d2ahzz8275ch1954cbh17326ah8275bhz2fh2a8h668h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h1155h) Received-SPF: pass (mail127-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=DB3PRD0310HT005.eurprd03.prod.outlook.com ; .outlook.com ; Received: from mail127-ch1 (localhost.localdomain [127.0.0.1]) by mail127-ch1 (MessageSwitch) id 1355865636979980_1355; Tue, 18 Dec 2012 21:20:36 +0000 (UTC) Received: from CH1EHSMHS022.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.239]) by mail127-ch1.bigfish.com (Postfix) with ESMTP id EC60A200253; Tue, 18 Dec 2012 21:20:36 +0000 (UTC) Received: from DB3PRD0310HT005.eurprd03.prod.outlook.com (157.56.252.5) by CH1EHSMHS022.bigfish.com (10.43.70.22) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 18 Dec 2012 21:20:32 +0000 Received: from [192.168.178.29] (88.71.28.19) by pod51013.outlook.com (10.255.44.40) with Microsoft SMTP Server (TLS) id 14.16.245.2; Tue, 18 Dec 2012 21:20:30 +0000 Message-ID: <50D0DE1B.7040301@innogames.de> Date: Tue, 18 Dec 2012 22:20:27 +0100 From: Bernhard Schrader User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Tom Lane CC: Andrew Dunstan , Andres Freund , Bruce Momjian , PostgreSQL-development Subject: Re: [ADMIN] Problems with enums after pg_upgrade 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> <20121218183916.GA7666@awork2.anarazel.de> <12773.1355859273@sss.pgh.pa.us> <50D0C80D.90806@dunslane.net> <13661.1355860724@sss.pgh.pa.us> <50D0CFF7.5030606@dunslane.net> <9230.1355863093@sss.pgh.pa.us> In-Reply-To: <9230.1355863093@sss.pgh.pa.us> Content-Type: text/plain; charset="windows-1252"; format=flowed X-Originating-IP: [88.71.28.19] Content-Transfer-Encoding: quoted-printable X-OriginatorOrg: innogames.de X-Pg-Spam-Score: -2.6 (--) 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 12/18/2012 09:38 PM, Tom Lane wrote: > Andrew Dunstan writes: >> People have been known to hack pg_enum on their own, especially before >> we added enum extension. >> Of course, if they do that they get to keep both pieces. > Yeah ... this would be very readily explainable if there had been a > manual deletion from pg_enum somewhere along the line. Even if there > were at that time no instances of the OID left in tables, there could > be some in upper btree pages. They'd have caused no trouble in 9.0 > but would (if odd) cause trouble in 9.2. > > Of course, this theory doesn't explain why the problem was seen on some > copies and not others cloned from the same database --- unless maybe > there had been an index page split on the master in between the > clonings, and that moved the troublesome OID into a position where it > was more likely to get compared-to. That's not a hugely convincing > explanation though. > > regards, tom lane > Guys, thaaaaank youuu aaaall. :) reindex helped, did reindex on two=20 tables, and everything is now working like expected. I will provide tomorrow all information which could help to understand=20 everything in detail, but now it's gonna be late in germany :). and i=20 got a headache of all this stuff ^^ Thanks so much!!! --=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