Re: Periodic authorization expiration checks using GoAway message - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Periodic authorization expiration checks using GoAway message
Date
Msg-id CAOYmi+nXPkwam0RnF8ZChNnjeiTyPNa=grOcKZW3pzB2DUfY4Q@mail.gmail.com
Whole thread Raw
In response to Re: Periodic authorization expiration checks using GoAway message  (Zsolt Parragi <zsolt.parragi@percona.com>)
List pgsql-hackers
On Wed, Dec 17, 2025 at 2:44 AM Zsolt Parragi <zsolt.parragi@percona.com> wrote:
> * Some identity providers support pushing revocation data instead of
> pulling, and this usually works over HTTP. Which means that it needs a
> background process running a mini HTTP server (as part of an oauth
> validator).

(It's not really any of my business, but I feel compelled to say, as
someone who used to play the embedded web server game: HTTP server
implementations should be process-isolated away from Postgres shared
memory.)

--Jacob



pgsql-hackers by date:

Previous
From: Kirill Reshke
Date:
Subject: Re: GIN pageinspect support for entry tree and posting tree
Next
From: Heikki Linnakangas
Date:
Subject: Re: Reduce build times of pg_trgm GIN indexes