Re: RFC: Logging plan of the running query
torikoshia <torikoshia@oss.nttdata.com>
From: torikoshia <torikoshia@oss.nttdata.com>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Dilip Kumar
<dilipbalaut@gmail.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2021-07-09T05:05:16Z
Lists: pgsql-hackers
Attachments
- v5-0001-log-running-query-plan.patch (text/x-diff) patch v5-0001
On 2021-07-02 23:21, Bharath Rupireddy wrote: > On Tue, Jun 22, 2021 at 8:00 AM torikoshia <torikoshia@oss.nttdata.com> > wrote: >> Updated the patch. > > Thanks for the patch. Here are some comments on the v4 patch: Thanks for your comments and suggestions! I agree with you and updated the patch. On Thu, Jul 1, 2021 at 3:34 PM Fujii Masao <masao.fujii@oss.nttdata.com> wrote: > DO $$ > BEGIN > PERFORM pg_sleep(100); > END$$; > > When I called pg_log_current_query_plan() to send the signal to > the backend executing the above query, I got the following log message. > I think that this is not expected message. I guess this issue happened > because the information about query text and plan is retrieved > from ActivePortal. If this understanding is right, ISTM that we should > implement new mechanism so that we can retrieve those information > even while nested query is being executed. I'm now working on this comment. -- Regards, -- Atsushi Torikoshi NTT DATA CORPORATION
Commits
-
Allow GRANT on pg_log_backend_memory_contexts().
- f0b051e322d5 15.0 cited