Re: making EXPLAIN extensible
От | Robert Haas |
---|---|
Тема | Re: making EXPLAIN extensible |
Дата | |
Msg-id | CA+Tgmoa5sRYPoOyysuAaCxtg8OegJa0PhStDA-3rg0YbE1+z+g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: making EXPLAIN extensible (Andrei Lepikhov <lepihov@gmail.com>) |
Ответы |
Re: making EXPLAIN extensible
|
Список | pgsql-hackers |
On Tue, Mar 4, 2025 at 10:12 AM Andrei Lepikhov <lepihov@gmail.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
В списке pgsql-hackers по дате отправления: