| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Dave Cramer <pg(at)fastcrypt(dot)com> |
| Subject: | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |
| Date: | 2016-01-13 16:12:01 |
| Message-ID: | CAB=Je-G32oaYHpJFNL-ECfDoA+VVAHBf0nV_huCMq77XBeiAtg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
>If plan is ok for one value parameters, then can be pretty bad for following parameters.
Happy statements are all alike; every unhappy statement is unhappy in
its own way (see [1]).
If user is sending different kinds of parameters, he is shooting in the foot.
>Albe's proposal can be good enough for 2/3 cases and it doesn't block any other enhancing
Albe's proposal effectively disables plan cache, thus it blocks enhancing.
If a user goes "replan every time" route, there is no way you
introduce plan caching there.
[1]: https://en.wikipedia.org/wiki/Anna_Karenina_principle
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-01-13 16:24:03 | Re: pg_dump and premature optimizations for objects not to be dumped |
| Previous Message | Vladimir Sitnikov | 2016-01-13 15:57:59 | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-01-13 16:45:18 | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |
| Previous Message | Vladimir Sitnikov | 2016-01-13 15:57:59 | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |