From: Gregory Stark <stark@enterprisedb.com>
To: Henrik Zagerholm <henke@mac.se>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: Re: [PERFORM] Planner making wrong decisions 8.2.4. Insane cost calculations.
Date: Mon, 06 Aug 2007 16:31:14 +0100
Message-ID: <873aywn0hp.fsf@oxford.xeocode.com> (raw)
In-Reply-To: <A9EBAF31-5AEF-4F1C-B845-2D81D9936560@mac.se>
References: <0C963119-103A-4EB1-B9D8-0FD3E16A11F0@mac.se>
<87abt4n75m.fsf@oxford.xeocode.com>
<A9EBAF31-5AEF-4F1C-B845-2D81D9936560@mac.se>
"Henrik Zagerholm" <henke@mac.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
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: stark@enterprisedb.com, henke@mac.se, pgsql-general@postgresql.org
Subject: Re: [PERFORM] Planner making wrong decisions 8.2.4. Insane cost calculations.
In-Reply-To: <873aywn0hp.fsf@oxford.xeocode.com>
* 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