Re: Proposal: Progressive explain

From: Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info>
To: Rafael Thofehrn Castro <rafaelthca(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: Progressive explain
Date: 2025-01-14 21:55:15
Message-ID: 9b30b34b-ed3c-4859-a3f6-45094811780f@anayrat.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/30/24 2:18 AM, Rafael Thofehrn Castro wrote:
> Hello community,
>
> CONTEXT:
>
> Back in October I presented the talk "Debugging active queries with
> mid-flight instrumented explain plans" at PGConf EU 2024
> (recording: https://www.youtube.com/watch?v=6ahTb-7C05c) presenting
> an experimental feature that enables visualization of in progress
> EXPLAIN ANALYZE executions. Given the positive feedback and requests,
> I am sending this patch with the feature, which I am calling Progressive
> Explain.
>
> PROPOSAL:
>
> This proposal introduces a feature to print execution plans of active
> queries in an in-memory shared hash object so that other sessions can
> visualize them with a new view: pg_stat_progress_explain.

Hello
Thanks for your contribution! Such feature would be very useful.
I did not look carefully about the implementation. I just wanted to let
you know someone already posted a similar feature in this thread :
https://www.postgresql.org/message-id/CADdR5ny_0dFwnD%2BsuBnV1Vz6NDKbFHeWoV1EDv9buhDCtc3aAA%40mail.gmail.com

Maybe it could give you some ideas.

Regards,

--
Adrien NAYRAT

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-01-14 21:58:14 Re: Log a warning in pg_createsubscriber for max_slot_wal_keep_size
Previous Message Masahiko Sawada 2025-01-14 21:40:44 Re: Skip collecting decoded changes of already-aborted transactions