| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: making EXPLAIN extensible |
| Date: | 2025-03-04 15:14:18 |
| Message-ID: | CA+Tgmoa5sRYPoOyysuAaCxtg8OegJa0PhStDA-3rg0YbE1+z+g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 4, 2025 at 10:12 AM Andrei Lepikhov <lepihov(at)gmail(dot)com> wrote:
> Also, I think this feature is quite close to the discussion on the
> possibility of adding an extensible list field into Query, PlanState,
> Plan, etc. nodes to let extensions gather and transfer some additional
> data starting with the first 'analyze' hook up to the end of execution.
> For example, in solving user issues, I frequently need to know
> predictions on the number of groups in Memoize, IncrementalSort and some
> other nodes. Such extensibility could allow an extension to gather such
> internal data during the planning stage and show it in the explain
> without any changes in the core!
If you're saying there's a -hackers discussion on this, could you
provide a link? I haven't seen it.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-04 15:18:49 | Re: what's going on with lapwing? |
| Previous Message | Andrei Lepikhov | 2025-03-04 15:12:49 | Re: making EXPLAIN extensible |