Re: JDBC, prepared queries, and partitioning - Mailing list pgsql-jdbc

From Stephen Denne
Subject Re: JDBC, prepared queries, and partitioning
Date
Msg-id F0238EBA67824444BC1CB4700960CB4804A4F68C@dmpeints002.isotach.com
Whole thread Raw
In response to Re: JDBC, prepared queries, and partitioning  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-jdbc
Tom Lane wrote
> "Stephen Denne" <Stephen.Denne@datamail.co.nz> writes:
> > Isn't it more a case of
> > "even a minor variation in just one of this query's
> parameters can result in wildly different cost estimate,
> > so I really need to re-plan it every time."
>
> The $64 problem is not that; it is that certain optimizations will not
> be applied, period, unless the planner is dealing with values known
> at plan time.

Are there two problems:
1) My query could always be faster had the planner known the parameter values. (re Josh's inital question)
2) The chosen plan works fairly well in the general case, but for some parameter values it takes forever.

Stephen Denne.

Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer focus, and courage. This email with any
attachmentsis confidential and may be subject to legal privilege.  If it is not intended for you please advise by reply
immediately,destroy it and do not copy, disclose or use it in any way. 

__________________________________________________________________
  This email has been scanned by the DMZGlobal Business Quality
              Electronic Messaging Suite.
Please see http://www.dmzglobal.com/services/bqem.htm for details.
__________________________________________________________________



pgsql-jdbc by date:

Previous
From: Simon Riggs
Date:
Subject: Re: JDBC, prepared queries, and partitioning
Next
From: Simon Riggs
Date:
Subject: Re: JDBC, prepared queries, and partitioning