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 1331F52C2E for ; Thu, 14 Jul 2005 19:32:04 -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 15609-04 for ; Thu, 14 Jul 2005 22:31:55 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 8A0A652BC2 for ; Thu, 14 Jul 2005 19:31:53 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j6EMQppM008021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 14 Jul 2005 16:26:54 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.3/8.13.3) with ESMTP id j6EMQpHq023976; Thu, 14 Jul 2005 16:26:51 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j6EMQpBf023975; Thu, 14 Jul 2005 16:26:51 -0600 (MDT) (envelope-from mfuhr) Date: Thu, 14 Jul 2005 16:26:51 -0600 From: Michael Fuhr To: "Chris White (cjwhite)" Cc: pgsql-admin@postgresql.org Subject: Re: Error message: cannot identify operator 184 Message-ID: <20050714222651.GA23947@winnie.fuhr.org> References: <3175C4C5F682C145B25808EB5737F16C6250C2@xmb-sjc-21b.amer.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3175C4C5F682C145B25808EB5737F16C6250C2@xmb-sjc-21b.amer.cisco.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200507/102 X-Sequence-Number: 18158 On Thu, Jul 14, 2005 at 01:48:38PM -0700, Chris White (cjwhite) wrote: > Anybody have any idea why the error message "cannot identify operator > 184" should be output. Also, what does it mean as to the state of the > database, do we need to do anything to correct a problem? Is that the *exact* error message? Where did you see it? Can you tell us anything more about the context in which it was generated? -- Michael Fuhr http://www.fuhr.org/~mfuhr/