From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | cedric(at)2ndquadrant(dot)com |
Cc: | pgsql-performance(at)postgresql(dot)org, Guillaume Cottenceau <gc(at)mnc(dot)ch> |
Subject: | Re: non index use on LIKE on a non pattern string |
Date: | 2012-06-08 13:57:07 |
Message-ID: | 11641.1339163827@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
=?iso-8859-1?q?C=E9dric_Villemain?= <cedric(at)2ndquadrant(dot)com> writes:
>> I have noticed that with a SELECT query containing the following
>> constraint:
>>
>> column LIKE ?
>>
>> and an index on that column, PostgreSQL will not use the index
>> even if the parameter doesn't contain special pattern characters
>> such as %.
> you should have a postgresql 8.3,isn't it ?
> like is equal to "=" in your case, since 8.4
No, the planner has understood about wildcard-free LIKE patterns
producing an "=" index condition at least since 7.3. I think what the
OP is complaining about is the problem that the pattern has to be
actually constant (ie, NOT a parameter) before it can be optimized into
an index condition. This should be better in 9.2 ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-06-08 14:10:58 | Re: how to change the index chosen in plan? |
Previous Message | Rural Hunter | 2012-06-08 13:33:08 | how to change the index chosen in plan? |