Re: Proposal: Progressive explain

Rafael Thofehrn Castro <rafaelthca@gmail.com>

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

To: Robert Haas <robertmhaas@gmail.com>

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

Date: 2025-03-28T20:12:40Z

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

> That is correct. Interval currently is only used when instrumentation
> is enabled through progressive_explain = analyze.

I guess there would still be a point in printing the plan on a regular
interval
when instrumentation is disabled. In that case the only thing we would see
changing in the plan is the node currently being executed. But with that we
add more overhead to progressive_explain = 'explain', that in that case will
also require a custom execProcNode wrapper.