Re: RFC: Logging plan of the running query
От | torikoshia |
---|---|
Тема | Re: RFC: Logging plan of the running query |
Дата | |
Msg-id | 958b590c8195aa2b3b3c57755c40b3ba@oss.nttdata.com обсуждение исходный текст |
Ответ на | Re: RFC: Logging plan of the running query (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>) |
Список | pgsql-hackers |
On 2021-11-15 23:15, Bharath Rupireddy wrote: > I have another comment: isn't it a good idea that an overloaded > version of the new function pg_log_query_plan can take the available > explain command options as a text argument? I'm not sure if it is > possible to get the stats like buffers, costs etc of a running query, > if yes, something like pg_log_query_plan(pid, 'buffers', > 'costs'....);? It looks to be an overkill at first sight, but these > can be useful to know more detailed plan of the query. I also think the overloaded version would be useful. However as discussed in [1], it seems to introduce other difficulties. I think it would be enough that the first version of pg_log_query_plan doesn't take any parameters. [1] https://www.postgresql.org/message-id/ce86e4f72f09d5497e8ad3a162861d33%40oss.nttdata.com -- Regards, -- Atsushi Torikoshi NTT DATA CORPORATION
В списке pgsql-hackers по дате отправления: