| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: On-demand running query plans using auto_explain and signals |
| Date: | 2015-09-29 10:57:25 |
| Message-ID: | 20150929105725.GL5702@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-09-25 19:13:13 +0200, Shulgin, Oleksandr wrote:
> the auto_explain contrib module. I now propose the most simple thing
> possible in my opinion: a new GUC option for auto_explain. It will make
> every backend, in which the module is loaded via *_preload_libraries
> mechanism or using CREATE EXTENSION/LOAD commands, to actively publish the
> plans of queries in dynamic shared memory as long as
> auto_explain.publish_plans is turned on.
Wait. You're proposing that every query does this unconditionally? For
every single query? That sounds prohibitively expensive to me.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2015-09-29 11:00:28 | Re: Foreign join pushdown vs EvalPlanQual |
| Previous Message | Shulgin, Oleksandr | 2015-09-29 10:52:11 | Re: On-demand running query plans using auto_explain and signals |