| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Shay Rojansky <roji(at)roji(dot)org> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Greg Stark <stark(at)mit(dot)edu>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Slowness of extended protocol |
| Date: | 2016-08-11 08:39:05 |
| Message-ID: | CAB=Je-GZNHrxEG4GhtXizkt0nhxCH=h-Q=vu7=P0xE_moErMgQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Shay:
> Prepared statements can have very visible effects apart from the speedup
> they provide (e.g. failure because of schema changes) It's not that these
> effects can't be worked around - they can be - but programmers can be
> surprised by these effects, which can cause difficult-to-diagnose issues.
>
The specific effect of "cached plan cannot change return type" can be
solved by cooperation of backend and frontend (~driver) developers.
I find that solving that kind of issues is more important than investing
into "ParseBindExecDeallocateInOneGo" message.
I hope you would forgive me if I just stop the discussion here.
I find I'd better spent that time on just fixing pgbouncer issue rather
than discussing if it is pgbouncer's or postgresql's issue.
I'm sorry for being impolite if I was ever.
Vladimir
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2016-08-11 09:01:18 | Re: Assertion failure in REL9_5_STABLE |
| Previous Message | Shay Rojansky | 2016-08-11 08:11:38 | Re: Slowness of extended protocol |