Re: RFC: Logging plan of the running query

torikoshia <torikoshia@oss.nttdata.com>

From: torikoshia <torikoshia@oss.nttdata.com>

To: Atsushi Torikoshi <torikoshia.tech@gmail.com>, robertmhaas@gmail.com

Cc: pgsql-hackers@lists.postgresql.org, samimseih@gmail.com, destrex271@gmail.com, torikoshia.tech@gmail.com, robertmhaas@gmail.com

Date: 2025-09-01T13:35:11Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

ecpg: Catch zero-length Unicode identifiers correctly
- a18b6d2dc288 15.0 cited
Improve warning message in pg_signal_backend()
- 7fa945b857cc 15.0 cited
Add assert to ensure that page locks don't participate in deadlock cycle.
- 72e78d831ab5 13.0 cited

Attachments

v46-0001-Add-function-to-log-the-plan-of-the-currently-ru.patch (text/x-diff) patch v46-0001

On 2025-06-02 21:56, torikoshia wrote:
> On 2025-05-23 17:50, Atsushi Torikoshi wrote:
>> Thanks for the idea and the sample patch!
>> Agreed. I’ll go ahead and implement a new patch based on this 
>> approach.

Rebased just because of doc refactoring.

-- 
Regards,

--
Atsushi Torikoshi
Seconded from NTT DATA Japan Corporation to SRA OSS K.K.