| From: | Mark Mielke <mark(at)mark(dot)mielke(dot)cc> |
|---|---|
| To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, PFC <lists(at)peufeu(dot)com>, Dawid Kuroczko <qnex42(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Cached Query Plans |
| Date: | 2008-04-14 14:55:58 |
| Message-ID: | 4803707E.9070301@mark.mielke.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I like cross-session query plan caching talk. I would prefer if the
function was optional (i.e. per-session "use cross-session query plan
cache" variable).
I like the "automatic re-plan if the estimate did not match the actual"
idea with some softening technique involved such as "if the last 3 times
it ran, it did the wrong thing, learn from our mistake and adapt".
The other ideas about automatically deciding between plans based on
ranges and such strike me as involving enough complexity and logic, that
to do properly, it might as well be completely re-planned from the
beginning to get the most benefit.
Cheers,
mark
--
Mark Mielke <mark(at)mielke(dot)cc>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Csaba Nagy | 2008-04-14 15:01:47 | Re: Cached Query Plans |
| Previous Message | PFC | 2008-04-14 14:51:10 | Re: Cached Query Plans (was: global prepared statements) |