| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | 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:06:08 |
| Message-ID: | Pine.BSO.4.64.0802131602540.9961@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Wed, 13 Feb 2008, Simon Riggs wrote:
> On Wed, 2008-02-13 at 15:43 -0500, Kris Jurka wrote:
>
>> No, in V3 all prepared statements are prepared regardless of the
>> threshold.
>
> Am I reading the wrong documentation?
> http://jdbc.postgresql.org/documentation/83/connect.html#connection-parameters
>
The documentation is just simplifying the complexities of named vs unnamed
statements. Aside from a couple of exceptions, an unnamed prepared
statement should perform equivalently to direct execution of the literal
query. Describing it as semi-prepared is complicated and not particularly
useful if there is no way to get non-prepared behavior.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-02-13 21:13:42 | Re: JDBC, prepared queries, and partitioning |
| Previous Message | Simon Riggs | 2008-02-13 20:56:21 | Re: JDBC, prepared queries, and partitioning |