Re: RFC: Logging plan of the running query

Поиск
Список
Период
Сортировка
Искать
От
Bharath Rupireddy
Тема
Re: RFC: Logging plan of the running query
Дата
в 09:27:56
Msg-id
CALj2ACXDiOhAdXks_w2b5NGg=7_K27Lx1Gau_iQnxGBCNkSMnQ@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Re: RFC: Logging plan of the running query Ekaterina Sokolova <e.sokolova@postgrespro.ru>
Re: RFC: Logging plan of the running query torikoshia <torikoshia@oss.nttdata.com>
Re: RFC: Logging plan of the running query Ekaterina Sokolova <e.sokolova@postgrespro.ru>
Re: RFC: Logging plan of the running query torikoshia <torikoshia@oss.nttdata.com>
Re: RFC: Logging plan of the running query torikoshia <torikoshia@oss.nttdata.com>
Re: RFC: Logging plan of the running query torikoshia <torikoshia@oss.nttdata.com>
Re: RFC: Logging plan of the running query Fujii Masao <masao.fujii@oss.nttdata.com>
Re: RFC: Logging plan of the running query Daniel Gustafsson <daniel@yesql.se>
On Thu, May 13, 2021 at 2:44 PM Dilip Kumar  wrote:
> +1 for the idea.  I did not read the complete patch but while reading
> through the patch, I noticed that you using elevel as LOG for printing
> the stack trace.  But I think the backend whose pid you have passed,
> the connected client to that backend might not have superuser
> privileges and if you use elevel LOG then that message will be sent to
> that connected client as well and I don't think that is secure.  So
> can we use LOG_SERVER_ONLY so that we can prevent
> it from sending to the client.

True, we should use LOG_SERVER_ONLY and not send any logs to the client.

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com


В списке pgsql-hackers по дате отправления
От: Dilip Kumar
Дата:
От: Bharath Rupireddy
Дата:
FAQ