Re: Surprising sequence scan when function call used

From: Hosokawa Tetsuichi <hosokawa(at)good-day(dot)co(dot)jp>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: Surprising sequence scan when function call used
Date: 2000-10-26 04:08:49
Message-ID: 20001026040849.BB795405E@poseidon.good-day.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

see
functional index

On Wed, 25 Oct 2000 13:26:51 -0400
"Will Fitzgerald" <fitzgerald(at)inetmi(dot)com> wrote:

> I have a table, login, which has a field by the same name; there's an index
> on that field. I was surprised to discover that a SELECT which compares the
> login field to a constant uses an Index scan, but if it is compared to a
> function call--for example, lower()--a sequence scan is forced.
>
> Any idea why?
--
* Hosokawa Tetsuichi
* hosokawa(at)good-day(dot)co(dot)jp

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2000-10-26 04:09:09 Re: plperl
Previous Message Tom Lane 2000-10-26 03:22:56 Re: Surprising sequence scan when function call used