| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Caching query plan costs |
| Date: | 2018-09-03 16:01:21 |
| Message-ID: | 20180903160121.GR30259@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
This email thread from last year:
got stuck on when to check for certain optimizations in the planner. It
was discussed that knowing a plan was going to be expensive _before_
planning could help determine when to try certain expensive
optimizations.
What if we globally or locally cache the _cost_ of plans, so we can
consult that cache before planning and enable certain optimizations? It
also might be useful to cache some of the unexpected things found during
execution, e.g. inaccurate cost estimates.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2018-09-03 17:14:41 | Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -r option) |
| Previous Message | Alexander Korotkov | 2018-09-03 15:16:02 | Re: A strange GiST error message or fillfactor of GiST build |