Re: RFC: Logging plan of the running query
От | Bharath Rupireddy |
---|---|
Тема | Re: RFC: Logging plan of the running query |
Дата | |
Msg-id | CALj2ACXDiOhAdXks_w2b5NGg=7_K27Lx1Gau_iQnxGBCNkSMnQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: RFC: Logging plan of the running query (Dilip Kumar <dilipbalaut@gmail.com>) |
Ответы |
Re: RFC: Logging plan of the running query
|
Список | pgsql-hackers |
On Thu, May 13, 2021 at 2:44 PM Dilip Kumar <dilipbalaut@gmail.com> 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 по дате отправления: