Re: making EXPLAIN extensible - Mailing list pgsql-hackers

From Robert Haas
Subject Re: making EXPLAIN extensible
Date
Msg-id CA+TgmoaTkMna7OMqP-bJ+70sVvhmc2pHZ8xa1dU6NVAWE=7Qrg@mail.gmail.com
Whole thread Raw
In response to Re: making EXPLAIN extensible  (Andrei Lepikhov <lepihov@gmail.com>)
Responses Re: making EXPLAIN extensible
List pgsql-hackers
On Thu, Mar 20, 2025 at 3:04 AM Andrei Lepikhov <lepihov@gmail.com> wrote:
> I'm sorry, I was confused; previously, the difficulties faced by
> extension developers were always attributed to him (refer to the
> discussion on the selectivity hook). However, now you're introducing a
> hook for a trivial operation that could simply be resolved at the end of
> execution within a per-node hook with tiny inconsistency in output. I'm
> pleased to see a change in the narrative.

It sounds like we're sufficiently in agreement so I've committed the
patch. I agree with you that this could be done within the per-node
hook, but that would be awkward, and this is better. I take note of
your frustration with the difficulty of getting hooks added and to
some extent I share it; on the flip side, there are plenty of
poorly-considered hook proposals, too.

I've rebased my pg_overexplain patch and attach that here.

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

Attachment

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: AIO v2.5
Next
From: Robert Haas
Date:
Subject: Re: why there is not VACUUM FULL CONCURRENTLY?