| From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Maciek Sakrejda <msakrejda(at)truviso(dot)com>, Radosław Smogura <rsmogura(at)softperience(dot)eu>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: binary patch problems |
| Date: | 2011-09-20 05:00:53 |
| Message-ID: | 4E781E05.5090203@ringerc.id.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 09/20/2011 08:39 AM, Tom Lane wrote:
> Maciek Sakrejda<msakrejda(at)truviso(dot)com> writes:
>> I think what Tom is saying is that you'll be able to set
>> prepareThreshold to 1 in the driver (always use named server-side
>> prepared statements) and the server will automagically do the right
>> thing. Right now, the big problem is that only unnamed prepared
>> statements include the "feature" of being able to consider parameters
>> in the query plan (since unnamed statements are not reused, there's no
>> sense in planning them before you have parameters).
> Right. We've rejiggered the backend so that planning is delayed until
> parameter values are available in all cases.
Oooh, exciting. That'll cut down on a whole class of mailing list query
and get rid of a classic gotcha.
Time for me to build git and start playing.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume | 2011-09-20 09:18:40 | Re: jdbc and automagic casting |
| Previous Message | Tom Lane | 2011-09-20 00:39:31 | Re: binary patch problems |