| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Subject: | Re: NOT EXIST for PREPARE |
| Date: | 2016-03-23 20:08:32 |
| Message-ID: | CAHyXU0x26Z6_M6sKN1vUO0pWbFtfo9PZ78WTsbS+eDoWChRzmg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 23, 2016 at 2:17 PM, Vladimir Sitnikov
<sitnikov(dot)vladimir(at)gmail(dot)com> wrote:
> Merlin>proposed would allow use of server side prepared statements with JDBC.
>
> It would not. If we discuss end-to-end scenarios in detail, we would end up with
> "send full query on each execution" -> lex/gram on each execution kind
> of overheads.
I think we're talking over each other here. I'm not suggesting the
jdbc driver needs to be adjusted. All I'm saying is that the use of
server side prepared statements is extremely problematic in
conjunction with pgbouncer (or any technology where the application db
connection and the server session are not 1:1) and trivial with the
proposed patch.
Any discussion regarding jdbc is off topic relative to that.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-03-23 20:10:13 | Re: NOT EXIST for PREPARE |
| Previous Message | Robert Haas | 2016-03-23 20:07:09 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |