From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Marc Mitchell <marcm(at)eisolution(dot)com> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: LIKE operator and indexes |
Date: | 2002-05-31 17:02:17 |
Message-ID: | 20020531095711.V56129-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, 31 May 2002, Marc Mitchell wrote:
> Can anyone provide definitive information and/or points of reference within
> the documentation about the ability of the query optimizer to use indexes
> when processing a "LIKE" operator on a String column?
>
> My assumption is that
>
> "SELECT * FROM customer WHERE name LIKE 'GENERAL%';"
>
> should benefit from the existence of a BTREE index on the "customer.name"
> column. I know this is the case is most other RDBMS's I've used including
> Postgres's ancestor Ingres.
If you are in "C" locale, and have an anchored like or regex, indexes
should be considered. If you're in a different locale, the optimization
is turned off.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-06-02 20:22:08 | Re: Authentication in batch processing |
Previous Message | Nick Fankhauser | 2002-05-31 16:44:02 | Re: LIKE operator and indexes |