Re: RFC: Logging plan of the running query
От | torikoshia |
---|---|
Тема | Re: RFC: Logging plan of the running query |
Дата | |
Msg-id | 0cc0608d89cc61a29e18c4ba8f8a03a6@oss.nttdata.com обсуждение исходный текст |
Ответ на | Re: RFC: Logging plan of the running query (Alena Rybakina <lena.ribackina@yandex.ru>) |
Ответы |
Re: RFC: Logging plan of the running query
|
Список | pgsql-hackers |
On 2022-09-21 17:30, Alena Rybakina wrote: Thanks for your reply! > I also noticed it. However I also discovered that above function > declarations to be aplied for explain command and used to be printed > details of the executed query. > > We have a similar task to print the plan of an interrupted process > making a request for a specific pid. > > In short, I think, this task is different and for separating these > parts I added this comment. I'm not sure I understand your comment correctly, do you mean HandleLogQueryPlanInterrupt() should not be placed in explain.c? It may be so. However, given that ProcesLogMemoryContextInterrupt(), which similarly handles interrupts for pg_log_backend_memory_contexts(), is located in mcxt.c, I also think current location might be acceptable. -- Regards, -- Atsushi Torikoshi NTT DATA CORPORATION
В списке pgsql-hackers по дате отправления: