Re: Add custom EXPLAIN options support to auto_explain

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Lukas Fittl <lukas(at)fittl(dot)com>
Cc: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Add custom EXPLAIN options support to auto_explain
Date: 2026-04-04 02:39:10
Message-ID: CA+TgmobanjKHqPqiZ9s5HYz0FMZSZsy4SEeJHzCudDdDYJXU+w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 3, 2026 at 10:09 PM Lukas Fittl <lukas(at)fittl(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-04-04 02:40:21 Re: Add pg_stat_autovacuum_priority
Previous Message Lukas Fittl 2026-04-04 02:09:00 Re: Add custom EXPLAIN options support to auto_explain