On Wed, Apr 21, 2010 at 11:30 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> On Tue, Apr 20, 2010 at 5:05 PM, Kris Jurka <books(at)ejurka(dot)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.
In response to
pgsql-performance by date
|Next:||From: Kris Jurka||Date: 2010-04-21 17:58:51|
|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
|Previous:||From: norn||Date: 2010-04-21 15:40:42|
|Subject: Re: significant slow down with various LIMIT|
pgsql-jdbc by date
|Next:||From: Shivender Devarakonda||Date: 2010-04-21 16:18:40|
|Subject: Re: Authentication failed when Password contains Japaneese Charecters|
|Previous:||From: Tom Lane||Date: 2010-04-21 15:30:26|
|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 |