Re: JDBC, prepared queries, and partitioning

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Stephen Denne" <Stephen(dot)Denne(at)datamail(dot)co(dot)nz>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Kris Jurka" <books(at)ejurka(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "PostgreSQL - JDBC" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: JDBC, prepared queries, and partitioning
Date: 2008-02-13 21:50:38
Message-ID: 24210.1202939438@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

"Stephen Denne" <Stephen(dot)Denne(at)datamail(dot)co(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Simon Riggs 2008-02-13 21:55:56 Re: JDBC, prepared queries, and partitioning
Previous Message Stephen Denne 2008-02-13 21:45:52 Re: JDBC, prepared queries, and partitioning