Re: making EXPLAIN extensible

Andrei Lepikhov <lepihov@gmail.com>

From: Andrei Lepikhov <lepihov@gmail.com>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Sami Imseih <samimseih@gmail.com>, Jeff Davis <pgsql@j-davis.com>, Thom Brown <thom@linux.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>

Date: 2025-03-27T21:34: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 →

pg_overexplain: Use PG_MODULE_MAGIC_EXT.
- 83ccc85859f3 18.0 landed
pg_overexplain: Call previous hooks as appropriate.
- 9f0c36aea0fb 18.0 landed
pg_overexplain: Additional EXPLAIN options for debugging.
- 8d5ceb113e3f 18.0 landed
Add an additional hook for EXPLAIN option validation.
- 50ba65e73325 18.0 landed
Add some new hooks so extensions can add details to EXPLAIN.
- 4fd02bf7cf94 18.0 landed
Make it possible for loadable modules to add EXPLAIN options.
- c65bc2e1d14a 18.0 landed

Attachments

v0-0001-Add-into-pg_overexplain-example-on-a-hook-call-ch.patch (text/x-patch) patch v0-0001

On 3/26/25 19:09, Robert Haas wrote:
> On Sat, Mar 22, 2025 at 12:10 PM Robert Haas <robertmhaas@gmail.com> wrote:
>> I'm not going
>> to insist on shipping this if I'm the ONLY one who would ever get any
>> use out of it, but I doubt that's the case.
> 
> Hearing no other votes against this, I have committed it, but now I
> wonder if that is going to break the buildfarm, because I just noticed
> that the changes I made in v9 seem not to have resolved the problem
> with debug_parallel_query, for reasons I do not yet understand.
> Investigating...
I’m afraid to sound like a bore, but I think pg_overexplain should 
include a call into the hook call chain (see attachment). Who knows, 
maybe this extension will be used someday in production?

-- 
regards, Andrei Lepikhov