| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | "Chris White (cjwhite)" <cjwhite(at)cisco(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Error message: cannot identify operator 184 |
| Date: | 2005-07-15 05:18:27 |
| Message-ID: | 7788.1121404707@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Michael Fuhr <mike(at)fuhr(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-07-15 13:16:41 | Re: functions vs stored procedures |
| Previous Message | Michael Fuhr | 2005-07-15 03:07:52 | Re: Error message: cannot identify operator 184 |