From: | Hannu Krosing <hannuk(at)google(dot)com> |
---|---|
To: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com> |
Cc: | Atsushi Torikoshi <torikoshia(dot)tech(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, samimseih(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org, destrex271(at)gmail(dot)com |
Subject: | Re: RFC: Logging plan of the running query |
Date: | 2025-04-27 23:55:31 |
Message-ID: | CAMT0RQTSGrjqEooQKEJ4X1oQ-OUAw8Zw0fKjSANRkscV0cc0yQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)oss(dot)nttdata(dot)com> wrote:
>
> Hi,
>
> Attached a rebased version of the patch.
>
> --
> Regards,
>
> --
> Atsushi Torikoshi
> Seconded from NTT DATA GROUP CORPORATION to SRA OSS K.K.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2025-04-28 00:12:30 | Re: Avoid circular header file dependency |
Previous Message | Ilia Evdokimov | 2025-04-27 19:58:52 | Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment |