Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id F0DDF632971
	for <pgsql-jdbc-postgresql.org@mail.postgresql.org>;
	Wed, 21 Apr 2010 12:30:39 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia,
	port 10024) with ESMTP id 40913-04 for
	<pgsql-jdbc-postgresql.org@mail.postgresql.org>;
	Wed, 21 Apr 2010 15:30:29 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 4FEBE6321E1
	for <pgsql-jdbc@postgresql.org>; Wed, 21 Apr 2010 12:30:29 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o3LFUQMP024145;
	Wed, 21 Apr 2010 11:30:26 -0400 (EDT)
To: Nikolas Everett <nik9000@gmail.com>
cc: Robert Haas <robertmhaas@gmail.com>, Kris Jurka <books@ejurka.com>,
	Dave Crooke <dcrooke@gmail.com>,
	Kevin Grittner <Kevin.Grittner@wicourts.gov>, pgsql-jdbc@postgresql.org,
	pgsql-performance <pgsql-performance@postgresql.org>,
	Scott Carey <scott@richrelevance.com>
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
In-reply-to: <q2qd4e11e981004210807ua364abbbua4ae2fb0a91ac053@mail.gmail.com> 
References: <q2sca24673e1004191633j10b1124amf1eb51f3bd84f19a@mail.gmail.com>
	<4BCD73AF0200002500030BC2@gw.wicourts.gov>
	<w2kca24673e1004200847k77429a1cra0a6f3560d407d8e@mail.gmail.com>
	<4BCD90D80200002500030BDD@gw.wicourts.gov>
	<x2zca24673e1004201229n653f4e69vd274af4a4aa22d09@mail.gmail.com>
	<4BCDC6B90200002500030C09@gw.wicourts.gov>
	<w2oca24673e1004201340p703b0121iaf852aa28695be65@mail.gmail.com>
	<alpine.BSO.2.00.1004201644280.6736@leary.csoft.net>
	<g2w603c8f071004210741y69db6e92p5a7d18c4fc2940a@mail.gmail.com>
	<q2qd4e11e981004210807ua364abbbua4ae2fb0a91ac053@mail.gmail.com>
Comments: In-reply-to Nikolas Everett <nik9000@gmail.com>
	message dated "Wed, 21 Apr 2010 11:07:11 -0400"
Date: Wed, 21 Apr 2010 11:30:26 -0400
Message-ID: <24144.1271863826@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201004/55
X-Sequence-Number: 20466

>> 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