X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DDF3452AB5 for ; Fri, 15 Jul 2005 02:18:35 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 39410-01 for ; Fri, 15 Jul 2005 05:18:31 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9A98252D07 for ; Fri, 15 Jul 2005 02:18:29 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j6F5IR1B007789; Fri, 15 Jul 2005 01:18:27 -0400 (EDT) To: Michael Fuhr Cc: "Chris White (cjwhite)" , pgsql-admin@postgresql.org Subject: Re: Error message: cannot identify operator 184 In-reply-to: <20050715030752.GA24612@winnie.fuhr.org> References: <3175C4C5F682C145B25808EB5737F16C62511A@xmb-sjc-21b.amer.cisco.com> <20050715030752.GA24612@winnie.fuhr.org> Comments: In-reply-to Michael Fuhr message dated "Thu, 14 Jul 2005 21:07:52 -0600" Date: Fri, 15 Jul 2005 01:18:27 -0400 Message-ID: <7788.1121404707@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200507/109 X-Sequence-Number: 18165 Michael Fuhr writes: > I'm wondering if the error means you're missing that function, which > is used to compare oid values. A system without oideq would be so dead in the water it's not funny --- consider that all the major catalogs are indexed by oid. It sounds to me that one particular index's "strategy map" (ie, its in-memory copy of the relevant indexable-operator info) got trashed. It's hard to guess why though. Could have been a hardware problem (RAM dropped a bit) or a software problem (wild store that happened to trash this data structure rather than anything else). regards, tom lane