| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Miroslav Šulc <miroslav(dot)sulc(at)startnet(dot)cz> |
| Cc: | PFC <lists(at)boutiquenumerique(dot)com>, 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 16:23:36 |
| Message-ID: | 14079.1110817416@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
=?ISO-8859-15?Q?Miroslav_=A6ulc?= <miroslav(dot)sulc(at)startnet(dot)cz> writes:
> PFC wrote:
>> Instead of a varchar(1) containing 'y' or 'n' you could use a BOOL
>> or an integer.
> Sure I could. The problem is our project still supports both MySQL and
> PostgreSQL. We used enum('Y','N') in MySQL so there would be a lot of
> changes in the code if we would change to the BOOL data type.
Just FYI, I did a quick search-and-replace on your dump to replace
varchar(1) by "char", which makes the column fixed-width without any
change in the visible data. This made hardly any difference in the
join speed though :-(. So that is looking like a dead end.
John's idea about re-joining to the main table to pick up the bulk of
its fields only after joining to the sub-tables might work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Miroslav Šulc | 2005-03-14 16:33:44 | Re: How to read query plan |
| Previous Message | Dennis Bjorklund | 2005-03-14 15:59:28 | Re: [BUGS] We are not following the spec for HAVING without |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Miroslav Šulc | 2005-03-14 16:33:44 | Re: How to read query plan |
| Previous Message | Greg Stark | 2005-03-14 15:58:55 | Re: How to read query plan |