From: Miroslav ulc <miroslav.sulc@startnet.cz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgreSQL.org
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: [PERFORM] How to read query plan
Date: Mon, 14 Mar 2005 16:21:37 +0100
Message-ID: <4235AC01.600@startnet.cz> (raw)
In-Reply-To: <13458.1110812581@sss.pgh.pa.us>
References: <42345D24.8070104@startnet.cz>
<4234692E.3050802@arbash-meinel.com>
<42347407.2000202@startnet.cz>
<423478B1.7080106@arbash-meinel.com>
<18381.1110741354@sss.pgh.pa.us>
<423497FE.6040908@startnet.cz>
<19293.1110743673@sss.pgh.pa.us>
<42349C96.60401@startnet.cz>
<3174.1110745587@sss.pgh.pa.us>
<4234AF56.1040509@startnet.cz>
<6715.1110758921@sss.pgh.pa.us>
<42354EA7.4020907@startnet.cz>
<13458.1110812581@sss.pgh.pa.us>
Tom Lane wrote:
>=?windows-1250?Q?Miroslav_=8Aulc?= <miroslav.sulc@startnet.cz> writes:
>
>
>>As there are a lot of varchar(1) in the AdDevicesSites table, wouldn't
>>be helpful to change them to char(1)? Would it solve the variable-width
>>problem at least for some fields and speed the query up?
>>
>>
>
>No, because char(1) isn't physically fixed-width (consider multibyte
>encodings). There's really no advantage to char(N) in Postgres.
>
>
I was aware of that :-(
>I don't know what you're doing with those fields, but if they are
>effectively booleans or small codes you might be able to convert them to
>bool or int fields. There is also the "char" datatype (not to be
>confused with char(1)) which can hold single ASCII characters, but is
>nonstandard and a bit impoverished as to functionality.
>
>
The problem lies in migration from MySQL to PostgreSQL. In MySQL we
(badly) choose enum for yes/no switches (there's nothing like boolean
field type in MySQL as I know but we could use tinyint). It will be very
time consuming to rewrite all such enums and check the code whether it
works.
>However, I doubt this is worth pursuing. One of the things I tested
>yesterday was a quick hack to organize the storage of intermediate join
>tuples with fixed-width fields first and non-fixed ones later. It
>really didn't help much at all :-(. I think the trouble with your
>example is that in the existing code, the really fast path applies only
>when the tuple contains no nulls --- and since you're doing all that
>left joining, there's frequently at least one null lurking.
>
>
Unfortunatelly I don't see any other way than LEFT JOINing in this case.
> regards, tom lane
>
>
Miroslav
Attachments:miroslav.sulc.vcf (text/x-vcard, 385B) download
begin:vcard
fn;quoted-printable:Miroslav =C5=A0ulc
n;quoted-printable:=C5=A0ulc;Miroslav
org:StartNet s.r.o.
adr;quoted-printable;quoted-printable:;;Vrchlick=C3=A9ho 161/5;Praha 5;;150 00;=C4=8Cesk=C3=A1 republika
email;internet:miroslav.sulc@startnet.cz
title:CEO
tel;work:+420 257 225 602
tel;cell:+420 603 711 413
x-mozilla-html:TRUE
url:http://www.startnet.cz
version:2.1
end:vcard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: miroslav.sulc@startnet.cz, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
Subject: Re: [PERFORM] How to read query plan
In-Reply-To: <4235AC01.600@startnet.cz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox