Re: [HACKERS] Help: fmgr_info: function 0: cache lookup failed - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Help: fmgr_info: function 0: cache lookup failed
Date
Msg-id 12945.927731190@sss.pgh.pa.us
Whole thread Raw
In response to Help: fmgr_info: function 0: cache lookup failed  ("D'Arcy" "J.M." Cain <darcy@druid.net>)
Responses Re: [HACKERS] Help: fmgr_info: function 0: cache lookup failed  ("D'Arcy" "J.M." Cain <darcy@druid.net>)
List pgsql-hackers
darcy@druid.net ("D'Arcy" "J.M." Cain) writes:
> darcy=> select * from x where g = '12345-0000';
> ERROR:  fmgr_info: function 0: cache lookup failed

> As you can see, the select worked until I added the index.

This is a bit of a reach, but maybe it would work if you added
commutator links to your operator definitions?  You should add 'em
anyway on general principles.

If that *does* fix it, I'd say it's still a bug; index operators
should not have to have commutator links.

Next step would be to burrow in with a debugger and figure out what
function the thing thinks it's trying to call.  A backtrace from
the call to elog() would help here.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Memory leak in large objects (was Re: Postgreqsl Large Objects)
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] I can't compile cvs snapshot ...