Horton

Re: Add custom EXPLAIN options support to auto_explain

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Lukas Fittl <lukas@fittl.com>
Cc: Matheus Alcantara <matheusssilv97@gmail.com>, pgsql-hackers@lists.postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2026-04-04T02:39:10Z
Lists: pgsql-hackers 
On Fri, Apr 3, 2026 at 10:09 PM Lukas Fittl <lukas@fittl.com> wrote:
> Hmm. I think it would be typical to set
> "auto_explain.log_extension_options" in postgresql.conf, and this
> requirement of needing to put the libraries in the right order to
> avoid the warning doesn't seem great. As a general principle, I think
> we should aim to not have any ordering requirements in
> shared_preload_libraries.

I agree, but we're pretty far from that already today, and I don't see
a way to avoid having this patch buy into it. And we're really,
super-duper out of time at this point. We can throw this away, but we
can't keep changing our minds.

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

Commits

  1. auto_explain: Add new GUC, auto_explain.log_extension_options.

  2. Add a guc_check_handler to the EXPLAIN extension mechanism.

  3. Expose helper functions scan_quoted_identifier and scan_identifier.