| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Miroslav ©ulc <miroslav(dot)sulc(at)startnet(dot)cz> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, John Arbash Meinel <john(at)arbash-meinel(dot)com>, PGSQL mailing list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: How to read query plan |
| Date: | 2005-03-14 15:58:55 |
| Message-ID: | 877jkauslc.fsf@stark.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Miroslav ©ulc <miroslav(dot)sulc(at)startnet(dot)cz> writes:
> I think so. I'll change the varchar(1) fields to char(1) where possible
char isn't faster than varchar on postgres. If anything it may be slightly
slower because every comparison first needs to pad both sides with spaces.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Bjorklund | 2005-03-14 15:59:28 | Re: [BUGS] We are not following the spec for HAVING without |
| Previous Message | John Arbash Meinel | 2005-03-14 15:54:29 | Re: [PERFORM] How to read query plan |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-14 16:23:36 | Re: How to read query plan |
| Previous Message | John Arbash Meinel | 2005-03-14 15:54:29 | Re: [PERFORM] How to read query plan |