From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Fuhr <mike@fuhr.org>
Cc: Chris White (cjwhite) <cjwhite@cisco.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Error message: cannot identify operator 184
Date: Fri, 15 Jul 2005 01:18:27 -0400
Message-ID: <7788.1121404707@sss.pgh.pa.us> (raw)
In-Reply-To: <20050715030752.GA24612@winnie.fuhr.org>
References: <3175C4C5F682C145B25808EB5737F16C62511A@xmb-sjc-21b.amer.cisco.com>
<20050715030752.GA24612@winnie.fuhr.org>
Michael Fuhr <mike@fuhr.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, mike@fuhr.org, cjwhite@cisco.com
Subject: Re: Error message: cannot identify operator 184
In-Reply-To: <7788.1121404707@sss.pgh.pa.us>
References: <3175C4C5F682C145B25808EB5737F16C62511A@xmb-sjc-21b.amer.cisco.com> <20050715030752.GA24612@winnie.fuhr.org> <7788.1121404707@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox