| From: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 8.3devel slower than 8.2 under read-only load |
| Date: | 2007-11-26 00:54:44 |
| Message-ID: | 1d4e0c10711251654v14462479x41a61ba50511518b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 26, 2007 1:35 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Smet | 2007-11-26 01:05:18 | Re: 8.3devel slower than 8.2 under read-only load |
| Previous Message | Tom Lane | 2007-11-26 00:35:23 | Re: 8.3devel slower than 8.2 under read-only load |