From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Docs off on ILIKE indexing? |
Date: | 2006-01-17 14:44:30 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C7EB6@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
> > http://www.postgresql.org/docs/8.1/static/indexes-types.html
> > says:
> > The optimizer can also use a B-tree index for queries involving the
> > pattern matching operators LIKE, ILIKE, ~, and ~*, if the
> pattern is a
> > constant and is anchored to the beginning of the string -
> for example,
> > col LIKE 'foo%' or col ~ '^foo', but not col LIKE '%bar'.
>
> > But really, does it use indexes for ILIKE?
>
> That's pretty poorly phrased. For ILIKE it'll only work if
> there's a prefix of the pattern that's not letters (and hence
> is unaffected by the case-folding issue).
Ahh. That explains it. Perfectly logical.
And yes, that's pretty poorly phrased - at least I didn't understand it
:-)
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-01-17 17:14:09 | vacuum and routine maintenance docs |
Previous Message | Gavin Sherry | 2006-01-16 00:20:16 | Re: Problem with the Planner |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-01-17 14:52:10 | Re: Large Scale Aggregation (HashAgg Enhancement) |
Previous Message | Daniel Schuchardt | 2006-01-17 14:44:15 | Error working with Temporary Sequences in plpgsql in 8.1 (8.0 works fine) |