Re: RFC: Logging plan of the running query
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: torikoshia <torikoshia@oss.nttdata.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2021-05-13T09:27:56Z
Lists: 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
Commits
-
Allow GRANT on pg_log_backend_memory_contexts().
- f0b051e322d5 15.0 cited