From: | Miroslav Šulc <miroslav(dot)sulc(at)startnet(dot)cz> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | 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 09:09:38 |
Message-ID: | 423554D2.9000207@startnet.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Christopher Kings-Lynne wrote:
>> 1) in PostgreSQL I use 'varchar(1)' for a lot of fields and in MySQL
>> I use 'enum'
>> 2) in PostgreSQL in some cases I use connection fields that are not
>> of the same type (smallint <-> integer (SERIAL)), in MySQL I use the
>> same types
>
>
> Well both those things will make PostgreSQL slower...
I think so. I'll change the varchar(1) fields to char(1) where possible
and will think out what I will do with the smallint <-> integer JOINs.
Something like SMALLSERIAL would be pleasant :-) I thought I will wait
for Tom Lane's reaction to my improvement suggestions I have posted in
other mail but maybe he has a deep night because of different time zone.
>
> Chris
Miroslav
Attachment | Content-Type | Size |
---|---|---|
miroslav.sulc.vcf | text/x-vcard | 387 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2005-03-14 09:13:23 | Re: [BUGS] We are not following the spec for HAVING without GROUP |
Previous Message | PFC | 2005-03-14 09:08:48 | Re: How to read query plan |
From | Date | Subject | |
---|---|---|---|
Next Message | Miroslav Šulc | 2005-03-14 09:17:44 | Re: How to read query plan |
Previous Message | PFC | 2005-03-14 09:08:48 | Re: How to read query plan |