From: | Gene <genekhart(at)gmail(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | does prepareThreshold work? forced to use old driver |
Date: | 2007-02-26 16:12:53 |
Message-ID: | 430d92a20702260812le88fb59w3ec40089db7b54dd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc pgsql-performance |
hi!
I've been having some serious performance issues with
postgresql8.2/hibernate/jdbc due to postgres reusing bad cached query
plans. It doesn't look at the parameter values and therefore does not
use any partial indexes.
After trying to set prepareThreshold=0 in the connection string which
didnt work, even modifying the jdbc driver and forcing it to 0 and not
working I realized that it must be being ignored. After giving up
pretty much I tried a much older driver which doesn't use server
prepared statements at all the problem has gone away and it is once
again using the partial indexes. How can I get this to work properly
on the new jdbc driver? I don't really like having to use a 2 year old
driver to get good performance as you can imagine :)
Could someone point me to a jdbc src file where I could just disable
server-side prepared statements entirely?
--
thanks, G
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-02-26 16:19:29 | Re: bug with PGXADataSource in JNDI |
Previous Message | Mario Splivalo | 2007-02-26 16:12:35 | Re: Calling functions with table-based-type parametars |
From | Date | Subject | |
---|---|---|---|
Next Message | Madison Kelly | 2007-02-26 16:29:14 | Writting a "search engine" for a pgsql DB |
Previous Message | Peter Childs | 2007-02-26 15:53:17 | Re: Vacuumdb - Max_FSM_Pages Problem. |