The thing to remember here is that prepared statements are only planned once and strait queries are planned for each query.
When you give the query planner some concrete input like in your example then it will happily use the index because it can check if the input starts with % or _. If you use JDBC to set up a prepared statement like:
select df.id as id, df.c as c, df.href as href, df.existing as existing, df.filesize as filesize from documentfile df where (lower(href) like ? escape '!' ) order by id limit 1
then the query planner takes the safe route like Markus said and doesn't use the index.
I think your best bet is to use connection.createStatement instead of connection.prepareStatement. The gain in query performance will offset the loss in planning overhead. I'm reasonably sure the plans are cached anyway.
--Nik
On Mon, Feb 25, 2008 at 6:10 AM, Markus Bertheau <mbertheau.pg@xxxxxxxxxxxxxx> wrote:
2008/2/25, Pavel Rotek <pavel.rotek@xxxxxxxxx>:
> I have created functional index table(lower(href) varchar_pattern_ops)Most likely the problem is that the JDBC driver uses prepared statements, in
> because of lower case "like" searching. When i ask the database directly
> from psql, it returns result in 0,5 ms, but when i put the same command via
> jdbc driver, it returns in 10 000 ms. Where can be the problem?? Any problem
> with PostgreSQL tuning??
which the query is planned withouth the concrete argument value. For like only
patterns that don't start with % or _ can use the index. Without the argument
value PostgreSQL can't tell whether that is the case, so it takes the safe
route and chooses a sequential scan.
to solve this particular problem, you have to convince jdbc to not use a
prepared statement for this particular query.
Markus
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
