On Nov 26, 2007 1:35 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> The cost of resolving ambiguous operators has been an issue for a long
> time, of course, but it seems particularly bad in this case --- gprof
> blames 37% of the runtime on oper_select_candidate(). It might be time
> to think about caching the results of operator searches somehow. Too
> late for 8.3 though.
From what you say, I understand we can't even find a workaround for
8.3 to improve the situation while waiting for a cleaner solution in
8.4+?
At least, I'm glad we finally found an explanation for this problem.
Thanks.
--
Guillaume
