Re: Periodic authorization expiration checks using GoAway message

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: Ajit Awekar <ajitpostgres(at)gmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Hannu Krosing <hannuk(at)google(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Dave Cramer <davecramer(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Periodic authorization expiration checks using GoAway message
Date: 2026-01-06 16:46:37
Message-ID: CAOYmi+nXPkwam0RnF8ZChNnjeiTyPNa=grOcKZW3pzB2DUfY4Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 17, 2025 at 2:44 AM Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-01-06 17:00:23 Re: Reduce build times of pg_trgm GIN indexes
Previous Message Kirill Reshke 2026-01-06 16:44:54 Re: GIN pageinspect support for entry tree and posting tree