| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(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-12 16:16:54 |
| Message-ID: | CAFj8pRC3PUgJC85YS1b4iskWT=VB4-wvU=PBF0TJRyLBWgPmGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
2016-01-12 17:01 GMT+01:00 Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>:
> VS>>Why doesn't backend reuse already existing good plan?
> PS>this logic is driven by plan cost, not by plan execution time.
>
> It do understand that currently PG replans with $1, $2 and uses
> default selectivities for that.
>
> What I am asking is to make PG aware of "previously used bind values",
> so it would calculate proper selectivities for $1, $2.
>
the implementation is simply - but it hard to design some really general -
it is task for UI
Pavel
>
> PS. It is not the first time the problem bites me, so I hand-crafted a
> testcase.
>
>
> Vladimir
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2016-01-12 16:27:07 | Re: count_nulls(VARIADIC "any") |
| Previous Message | Vladimir Sitnikov | 2016-01-12 16:01:28 | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | C A M E X T E R I O R - INDUSTRIA - COMERCIO | 2016-01-13 00:01:35 | Exporte a Marruecos - Mision Comercial 25 Enero 2016 |
| Previous Message | Vladimir Sitnikov | 2016-01-12 16:01:28 | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |