| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, josh(at)agliodbs(dot)com, Stephen Denne <Stephen(dot)Denne(at)datamail(dot)co(dot)nz>, Kris Jurka <books(at)ejurka(dot)com>, PostgreSQL - JDBC <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: JDBC, prepared queries, and partitioning |
| Date: | 2008-02-14 06:46:06 |
| Message-ID: | 47B3E3AE.9050201@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Tom Lane wrote:
> Oliver Jowett <oliver(at)opencloud(dot)com> writes:
>> Another possibility is to make the unnamed statement behaviour in the
>> server more aggressive.
>
> Upthread I suggested making that conditional on a GUC variable ...
> does that seem reasonable?
That would be fine.
> For instance JDBC would
> need to expose an API to calling applications
I'm not sure why JDBC would need to do this .. in the current driver,
unnamed statements are only used for a single query execution anyway, so
turning on the GUC unconditionally would seem to be the way to go.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-02-14 07:13:23 | Re: JDBC, prepared queries, and partitioning |
| Previous Message | Tom Lane | 2008-02-14 05:59:26 | Re: JDBC, prepared queries, and partitioning |