From: | "Markus Bertheau" <mbertheau(dot)pg(at)googlemail(dot)com> |
---|---|
To: | "Pavel Rotek" <pavel(dot)rotek(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: response time when querying via JDBC and via psql differs |
Date: | 2008-02-25 11:10:32 |
Message-ID: | 684362e10802250310m48c45cb3lad3e70312ef4b3b6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
2008/2/25, Pavel Rotek <pavel(dot)rotek(at)gmail(dot)com>:
> I have created functional index table(lower(href) varchar_pattern_ops)
> 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??
Most likely the problem is that the JDBC driver uses prepared statements, in
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
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew | 2008-02-25 13:11:04 | Re: CORRECTION to msg 'loading same instance of dump to two different servers simultaneously' |
Previous Message | Pavel Rotek | 2008-02-25 10:06:16 | response time when querying via JDBC and via psql differs |