From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Marko Tiikkaja <marko(at)joh(dot)to>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, 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-18 19:14:11 |
Message-ID: | 6647.1453144451@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I never understood why we don't just keep the selectivity estimates of
> previous plans and just reuse the plan if the selectivity estimates are
> similar. Isn't parameter selectivity the only thing that distinguishes
> on plan with parameter from another?
> Checking selectivity estimates must be cheaper than replanning. This
> could be done at the second use of the prepared plan, and maybe for all
> plan reuses, rather than waiting for five and then perhaps getting this
> bad behavior.
You're imagining that a selectivity recheck could be separated out from
the rest of the planner. That's nowhere near feasible, IMO. Even if it
were, what would we do with it? There's no reliable way to determine
whether X% change in one or another selectivity number would change the
selected plan, other than by redoing practically all of the planning work.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Igal @ Lucee.org | 2016-01-18 19:23:34 | Re: Cannot find a working 64-bit integer type |
Previous Message | Glyn Astill | 2016-01-18 19:12:25 | Re: jsonb - jsonb operators |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2016-01-18 21:02:57 | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |
Previous Message | Bruce Momjian | 2016-01-18 18:55:22 | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |