public inbox for [email protected]
help / color / mirror / Atom feedFrom: Lukas Fittl <[email protected]>
To: Matheus Alcantara <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: [email protected]
Cc: Tom Lane <[email protected]>
Subject: Re: Add custom EXPLAIN options support to auto_explain
Date: Mon, 6 Apr 2026 12:50:59 -0700
Message-ID: <CAP53Pkw=EAceesLeD4dp4jPrAo+rXe1oHP97_ZfbxWM35mgE0Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CA+Tgmob-0W8306mvrJX5Urtqt1AAasu8pi4yLrZ1XfwZU-Uj1w@mail.gmail.com>
<CA+TgmoYUdeCdGfk8H6Ni2obXVixLvYaDkRGtxKLEmaCVNffsVA@mail.gmail.com>
<[email protected]>
<CA+TgmoacOujCREMtQwURTSokB+ks-eLgaQ5vBMdWG959XzFcrA@mail.gmail.com>
<CAP53PkwsnhmoLXJaUMKWc76S21GzYOX06qKyZdVZhGGW0rCWKw@mail.gmail.com>
<[email protected]>
On Mon, Apr 6, 2026 at 12:27 PM Matheus Alcantara
<[email protected]> wrote:
> My concern is about that some cloud providers expose
> shared_preload_libraries as a dropdown without user control over
> ordering. I can be totally wrong, but it seems to me that in this case,
> the provider would need to handle dependencies appropriately or have a
> way to let the user define the ordering. Or, a possible improvement
> would be a post-configuration validation hook that runs after all
> shared_preload_libraries are loaded, allowing deferred validation of
> cross-extension dependencies like these EXPLAIN options (I'm wondering
> that we can have more extension dependencies in the future, e.g
> plan_advice and pg_stat_statements [1])
>
> That said, I think we should proceed with 0003 as-is and revisit this
> when real-world usage reveals such problems in practice.
Agreed, I think we can lean on providers to do their part to make sure
this works.
FWIW, the main database-as-a-service provider I'm aware of that has a
drop down for shared_preload_libraries today is Azure, and they do use
alphabetic ordering in the UI. However I just checked, and the actual
shared_preload_libraries value is not alphabetic (e.g. they put
pg_cron first), so they just need to get the memo to handle this
correctly. FWIW, AWS allows specifying the list in the same way
postgresql.conf allows, and GCP has their own "cloudsql.enable_" flags
mechanism, which presumably can also be taught to do the right thing.
Thanks,
Lukas
--
Lukas Fittl
view thread (16+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Add custom EXPLAIN options support to auto_explain
In-Reply-To: <CAP53Pkw=EAceesLeD4dp4jPrAo+rXe1oHP97_ZfbxWM35mgE0Q@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox