Re: making EXPLAIN extensible - Mailing list pgsql-hackers

From Tom Lane
Subject Re: making EXPLAIN extensible
Date
Msg-id 137944.1742323219@sss.pgh.pa.us
Whole thread Raw
In response to Re: making EXPLAIN extensible  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: making EXPLAIN extensible
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> If you mean just after, that would amount to deciding that information
> coming from extensions goes before information from core rather than
> after. I thought about that and it's defensible, but in the end I
> thought it made more sense for core info to come first. We could
> bikeshed this endlessly, but there's no single choice that's going to
> make everybody 100% happy, and adding a whole bunch of extra hooks to
> cater to various preferences about exactly how the output should look
> does not seem worth it to me.

FWIW, I am fairly strongly against that.  Every extension author is
going to feel that their information is so important it should come
first.  Other people might have a different opinion about that, and
in any case they can't all be first.

There's certainly room for bikeshedding here, but I think it'd be good
to get some actual experience before redesigning what you've done.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: pg_stat_statements and "IN" conditions
Next
From: Robert Haas
Date:
Subject: Re: Update Unicode data to Unicode 16.0.0