Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 010C79FB38C for ; Mon, 26 Feb 2007 13:28:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 70374-01-3 for ; Mon, 26 Feb 2007 13:28:29 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by postgresql.org (Postfix) with SMTP id F407F9FB766 for ; Mon, 26 Feb 2007 13:28:29 -0400 (AST) Received: (qmail 20149 invoked from network); 26 Feb 2007 17:28:28 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.14?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 26 Feb 2007 17:28:28 -0000 In-Reply-To: <430d92a20702260812le88fb59w3ec40089db7b54dd@mail.gmail.com> References: <430d92a20702260812le88fb59w3ec40089db7b54dd@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <61223CAE-09EB-4FC0-987D-1542AA0F03F1@fastcrypt.com> Cc: pgsql-jdbc@postgresql.org, pgsql-performance@postgresql.org Content-Transfer-Encoding: 7bit From: Dave Cramer Subject: Re: does prepareThreshold work? forced to use old driver Date: Mon, 26 Feb 2007 12:28:37 -0500 To: gene@sotech.us X-Mailer: Apple Mail (2.752.3) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/133 X-Sequence-Number: 16689 On 26-Feb-07, at 11:12 AM, Gene wrote: > 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? > you can just add protocolVersion=2 to the url and it will not use prepared statements. setting prepareThreshold=0 just tells it not to use named statements. It will still use statements but won't cache them. Are you sure the problem is with cached statements ? There are issues where prepared statements won't use the index if you don't use the correct type. Dave > -- > thanks, G > > ---------------------------(end of > broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq >