From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Henrik Zagerholm" <henke(at)mac(dot)se> |
Cc: | <pgsql-performance(at)postgresql(dot)org>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: [PERFORM] Planner making wrong decisions 8.2.4. Insane cost calculations. |
Date: | 2007-08-06 15:31:14 |
Message-ID: | 873aywn0hp.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
"Henrik Zagerholm" <henke(at)mac(dot)se> writes:
> Ahh, my bad. It is a very small table but I have an unique index.
> CREATE UNIQUE INDEX tbl_filetype_suffix_idx ON tbl_filetype_suffix
> USING btree (filetype_suffix);
Well it can't use that to help with a join. If you had an index on
lower(filetype_suffix) it might be able to use it. I'm not sure though,
especially if it's a small table.
>> And any chance you could resend this stuff without the word-wrapping?
>> It's pretty hard to read like this:
>>
> Resending and hopefully the line breaks are gone. I couldn't find any
> in my sent mail.
No, the double-quotes are gone but the lines are still wrapped. It's become
quite a hassle recently to get mailers to do anything reasonable with code.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-06 15:31:51 | Re: [PERFORM] Planner making wrong decisions 8.2.4. Insane cost calculations. |
Previous Message | Brendon Sablinski | 2007-08-06 14:54:36 | Re: Asynchronous Query processing |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-06 15:31:51 | Re: [PERFORM] Planner making wrong decisions 8.2.4. Insane cost calculations. |
Previous Message | Tom Lane | 2007-08-06 14:58:47 | Re: Extreme slow select query 8.2.4 |