Re: RFC: Logging plan of the running query

From: Étienne BERSAC <etienne(dot)bersac(at)dalibo(dot)com>
To: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, jtc331(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: RFC: Logging plan of the running query
Date: 2023-10-27 07:06:31
Message-ID: 7bc1cc1bcc3289e9354ebb00ac1c8440c01b736c.camel@dalibo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hi Torikoshia,

> If so, we once tried to implement such function for getting memory
> contexts.
> However, this attempt didn't succeed because it could lead dead lock
> situation[1].

Thanks for the pointer. Why not use client log message to allow client
to get plan without locking backend memory context and without access
to server log ? I missed the rationnal for not sending the plan to
client.

Regards,
Étienne

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Étienne BERSAC 2023-10-27 07:14:38 Re: run pgindent on a regular basis / scripted manner
Previous Message Philip Warner 2023-10-27 07:05:30 RE: pg_dump not dumping the run_as_owner setting from version 16?