| From: | Arguile <arguile(at)lucentstudios(dot)com> |
|---|---|
| To: | Mike Mascari <mascarm(at)mascari(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Functional index performance question |
| Date: | 2003-09-30 14:30:25 |
| Message-ID: | 1064932226.26652.24.camel@broadswd |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2003-09-30 at 09:54, Mike Mascari wrote:
> Arguile wrote:
>
> > On Tue, 2003-09-30 at 07:06, Mike Mascari wrote:
> >
> >>CREATE INDEX i_employees ON employees(lower(name));
> >>
> >>Let's also assume that the lower() function is computationally
> >>expensive. Now if I have a query like:
> >>
> >>SELECT lower(name)
> >>FROM employees
> >>WHERE lower(name) = 'mike'
> >>
> >>will PostgreSQL re-evaluate lower(name)? Is it necessary?
> >
> > No, it won't re-evaluate.
>
> I think it will.
You're correct, I misunderstood to which clause you were referring to: I
thought you were wondering about the lower(name) in the where clause.
Sorry for the confusion.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-09-30 14:36:16 | Re: pg_hba.conf |
| Previous Message | Tom Lane | 2003-09-30 14:27:08 | Re: Functional index performance question |