| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(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 02:14:57 |
| Message-ID: | 871wadiwgu.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> But since your columns are varchar, which doesn't have any operators of its
> own, we have to go through oper_select_candidate()
I wonder whether at some point we shouldn't just eliminate this distinction
entirely. Just make "text" and "varchar" the same type and spell it "text"
when there's no typmod length restriction and "varchar(x)" when there is.
> 1. Datatype bloat: there are 58 "=" operators in pg_operator today,
> versus 54 at the beginning of the year. That's 7% more work right
> there to sort through the additional operators.
That's particularly scary because it means that databases which load piles of
contrib modules have that much more of an effect here. Some contrib modules
create a *lot* of operators.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-11-26 02:33:16 | Re: 8.3devel slower than 8.2 under read-only load |
| Previous Message | Tom Lane | 2007-11-26 01:55:45 | Re: quote_literal(integer) does not exist |