Horton

Re: RFC: Logging plan of the running query

Hannu Krosing <hannuk@google.com>

View thread
From: Hannu Krosing <hannuk@google.com>
To: torikoshia <torikoshia@oss.nttdata.com>
Cc: Atsushi Torikoshi <torikoshia.tech@gmail.com>, Robert Haas <robertmhaas@gmail.com>, samimseih@gmail.com, pgsql-hackers@lists.postgresql.org, destrex271@gmail.com
Date: 2025-04-27T23:55:31Z
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 →

  1. ecpg: Catch zero-length Unicode identifiers correctly

  2. Improve warning message in pg_signal_backend()

  3. Add assert to ensure that page locks don't participate in deadlock cycle.

Have you also checked out
https://github.com/postgrespro/pg_query_state which logs running query
plan AND collected counts and timings as a response to a signal?

Has this ever been discussed for inclusion in core ?

On Thu, Apr 24, 2025 at 2:49 PM torikoshia <torikoshia@oss.nttdata.com> wrote:
>
> Hi,
>
> Attached a rebased version of the patch.
>
> --
> Regards,
>
> --
> Atsushi Torikoshi
> Seconded from NTT DATA GROUP CORPORATION to SRA OSS K.K.