Re: making EXPLAIN extensible

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: making EXPLAIN extensible
Date: 2025-03-18 13:05:59
Message-ID: CA+Tgmoa+Yk8Pf80C1NgCu+ektyT=VZ_Wr+ZdZ0eTAC1RwKrp9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 17, 2025 at 11:54 PM Sami Imseih <samimseih(at)gmail(dot)com> wrote:
> +1
>
> I did not think of adding a new hook, because there must be a really good
> reason to add a new hook. I think it's justified for this case. It's better than
> my approach since the extension author can just put all their checks in one
> place rather than having to register a bunch of handlers.

Do you want to propose a patch?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2025-03-18 13:08:47 pgsql: Increase default maintenance_io_concurrency to 16
Previous Message Ranier Vilela 2025-03-18 12:46:54 Re: Show WAL write and fsync stats in pg_stat_io