public inbox for [email protected]  

help / color / mirror / Atom feed

From: Álvaro Herrera <[email protected]>
To: Zsolt Parragi <[email protected]>
Cc: Jacob Champion <[email protected]>
Cc: VASUKI M <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: [email protected]
Cc: Robert Haas <[email protected]>
Cc: [email protected]
Cc: Nikolay Shaplov <[email protected]>
Subject: Re: Custom oauth validator options
Date: Wed, 28 Jan 2026 17:23:39 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAN4CZFPmF9fGOcFubwOxqXymhVo_RvbUx3bLoYQcfk=f0mwECw@mail.gmail.com>

On 2026-Jan-28, Zsolt Parragi wrote:

> 0001: defines a new guc, guc_prefix_enforcement that potentially
> changes the behavior of prefix reservation. It has a few modes, based
> on which missing prefix reservations or variables defined outside the
> reserved prefix result in warnings or errors during library load time.
> This is unrelated to pgc_hba, and applies to all custom variables.

I didn't actually read this patch, but I wonder if this is something we
should attempt in the context of the larger refactoring done by the
patch series here,
https://postgr.es/m/2438819.yKrmzQ4Hd0@thinkpad-pgpro
I'm afraid it's likely to be very outdated at the moment, I think it'll
need a difficult rebase, but I invite you to have a look at what it
offered when it was last posted, and see if it would help write what
you're trying to achieve here.

Thanks

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"I'm always right, but sometimes I'm more right than other times."
                                                  (Linus Torvalds)
https://lore.kernel.org/git/[email protected]/

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], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Custom oauth validator options
  In-Reply-To: <[email protected]>

* 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