From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: making EXPLAIN extensible |
Date: | 2025-03-28 13:28:27 |
Message-ID: | CA+Tgmob01BMHAHU=M619SP_ZP=RXPv6ZsMUFw6ENat3azixsCQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Mar 28, 2025 at 5:39 AM Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> wrote:
> 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.
Yeah, I think this could make sense, but I'm not sure how much detail
to include. pg_overexplain is a little unusual in being one of few
contrib modules where all you have to do is load it -- there's no
CREATE EXTENSION required, and shared_preload_libraries is not
required either. So, it probably makes sense to explain something, but
if we eventually have 10 more modules that work like this, we wouldn't
want a lengthy explanation in each one.
Another thing that we might want to do is adjust the documentation for
EXPLAIN. At the very least, the "See also" section should probably
reference pg_overexplain, but we might also want some text there
explaining the general concept that EXPLAIN is now extensible via
loadable modules.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2025-03-28 13:55:52 | Re: 64 bit numbers vs format strings |
Previous Message | Amul Sul | 2025-03-28 13:27:51 | Re: NOT ENFORCED constraint feature |