| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Guillaume Smet" <guillaume(dot)smet(at)gmail(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 17:40:34 |
| Message-ID: | 874pf8dhwt.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> I've written up my suggestion as a 5 line patch, with measured
> performance improvement of about 40% for the varchar case.
A 5-line patch which improves performance by 40% for any case sounds amazing,
but how fragile is that gain? The kind of thing which would be worryign is if
runing a query which uses both varchar and some other ambiguous operator
causes it to lose all its gain.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2007-11-26 17:41:20 | Re: proposal, plpgsql, 8.4, for record in cursor |
| Previous Message | Bernd Helmle | 2007-11-26 17:32:39 | maintenance_work_mem memory constraint? |