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

From Tom Lane
Subject Re: JDBC, prepared queries, and partitioning
Date
Msg-id 24210.1202939438@sss.pgh.pa.us
Whole thread Raw
In response to Re: JDBC, prepared queries, and partitioning  ("Stephen Denne" <Stephen.Denne@datamail.co.nz>)
Responses Re: JDBC, prepared queries, and partitioning  ("Stephen Denne" <Stephen.Denne@datamail.co.nz>)
List pgsql-jdbc
"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.

            regards, tom lane

pgsql-jdbc by date:

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