Re: Proposal: Progressive explain

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Rafael Thofehrn Castro <rafaelthca@gmail.com>

Cc: Andrei Lepikhov <lepihov@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-03-28T20:01:55Z

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 →

Add some new hooks so extensions can add details to EXPLAIN.
- 4fd02bf7cf94 18.0 cited

On Fri, Mar 28, 2025 at 3:59 PM Rafael Thofehrn Castro
<rafaelthca@gmail.com> wrote:
> > True, although thinking about it more, they're not being sent to the
> > same place. auto_explain goes to the log, and this goes to a view.
> > What about something like this:
> > progressive_explain = on | off
> > progressive_explain_inteval = 5s
>
> I'm still more inclined to use:
>
> progressive_explain = off | explain | analyze
> progressive_explain_interval = any millisecond greater than a min threshold
> (currently 10ms). It doesn't make sense to be dumping the instrumented plan
> every 1ms for example, IMHO.

I still have trouble understanding what that means. Is the interval
irrelevant except when progressive_explain = analyze?

-- 
Robert Haas
EDB: http://www.enterprisedb.com