DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=Qv9hej5dhyOKTwagq4zd3H38yzSuqIxaHNlT0Rz1VxAM7Xrxl2WnhcvfQZylx5SQinCy4BTxiJ9TFXVXIkA8qkznp+acF2cVnVRbp6gPt34T9N/vezhTU9dDvNDZOKa46MCdPYH7N19p+HJz2pZSrmllL5yX/b5xFFPrz0VDbgo=
Message-ID: <430d92a20702260812le88fb59w3ec40089db7b54dd@mail.gmail.com>
Date: Mon, 26 Feb 2007 11:12:53 -0500
From: Gene <genekhart@gmail.com>
Reply-To: gene@sotech.us
To: pgsql-jdbc@postgresql.org, pgsql-performance@postgresql.org
Subject: does prepareThreshold work? forced to use old driver
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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