Re: SOLVED ... Re: Getting rid of a cursor from JDBC .... Re: [PERFORM] Re: HELP: How to tame the 8.3.x JDBC driver with a biq guery result set - Mailing list pgsql-jdbc

From Nikolas Everett
Subject Re: SOLVED ... Re: Getting rid of a cursor from JDBC .... Re: [PERFORM] Re: HELP: How to tame the 8.3.x JDBC driver with a biq guery result set
Date
Msg-id u2jd4e11e981004210843ya970697dp8e3d88dec74577ca@mail.gmail.com
Whole thread Raw
In response to Re: SOLVED ... Re: Getting rid of a cursor from JDBC .... Re: [PERFORM] Re: HELP: How to tame the 8.3.x JDBC driver with a biq guery result set  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-jdbc


On Wed, Apr 21, 2010 at 11:30 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> On Tue, Apr 20, 2010 at 5:05 PM, Kris Jurka <books@ejurka.com> wrote:
>>> ... There are three ways to plan a PreparedStatement:

FWIW, I think there is some consensus to experiment (in the 9.1 cycle)
with making the server automatically try replanning of parameterized
queries with the actual parameter values substituted.  It'll keep doing
so if it finds that that produces a significantly better plan than the
generic parameterized plan; which is what you'd expect if there's a
chance to optimize a LIKE search, eliminate partitions, etc.

                       regards, tom lane

That'd be wonderful.

pgsql-jdbc by date:

Previous
From: Tom Lane
Date:
Subject: Re: SOLVED ... Re: Getting rid of a cursor from JDBC .... Re: [PERFORM] Re: HELP: How to tame the 8.3.x JDBC driver with a biq guery result set
Next
From: Shivender Devarakonda
Date:
Subject: Re: Authentication failed when Password contains Japaneese Charecters