Re: making EXPLAIN extensible

Pavel Luzanov <p.luzanov@postgrespro.ru>

From: Pavel Luzanov <p.luzanov@postgrespro.ru>

To: pgsql-hackers@lists.postgresql.org

Date: 2025-03-28T09:39: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

One more suggestion to improve the documentation.
It lacks installations actions, something like in auto_explain:

To use pg_overexplain, simply load it into the server.
You can load it into an individual session:

LOAD 'pg_overexplain';

(You must be superuser to do that.)
Another way is to preload it into some or all sessions
by including pg_overexplain in session_preload_libraries
or shared_preload_libraries in postgresql.conf.

-- 
Pavel Luzanov
Postgres Professional:https://postgrespro.com