Re: Error message: cannot identify operator 184

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Michael Fuhr <mike@xxxxxxxx> 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


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux