Re: Custom oauth validator options - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: Custom oauth validator options
Date
Msg-id CAN4CZFPvjAt+eZJd=Rxp=yXRjva8CpJ_BbnF=vQW6uXCqfrjEg@mail.gmail.com
Whole thread Raw
In response to Re: Custom oauth validator options  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: Custom oauth validator options
List pgsql-hackers
> Might be more reason to look into the GUC system?

I am already thinking about that, I have some ideas for a proof of
concept, but no working prototype yet. But without requiring
shared_preload_libraries, we can't do early error reporting during
postmaster startup about custom parameters. Is that okay? GUCs already
work this way, and this could be a bit safer (reporting unknown
parameters/refusing to proceed during login, when we can completely
parse all parameters), but it would be different compared to how
pg_hba is handled currently.



pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Report bytes and transactions actually sent downtream
Next
From: Noah Misch
Date:
Subject: Re: Inval reliability, especially for inplace updates