Horton

Re: Periodic authorization expiration checks using GoAway message

Ajit Awekar <ajitpostgres@gmail.com>

View thread
From: Ajit Awekar <ajitpostgres@gmail.com>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Zsolt Parragi <zsolt.parragi@percona.com>, Jelte Fennema-Nio <postgres@jeltef.nl>, Hannu Krosing <hannuk@google.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Dave Cramer <davecramer@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>
Date: 2025-12-17T10:06:28Z
Lists: pgsql-hackers 
Background process will help us to gain performance so as it will be
seamless to users and user queries will not be impacted.

Thanks & Best Regards,
Ajit

On Wed, 17 Dec 2025 at 01:52, Jacob Champion <
jacob.champion@enterprisedb.com> wrote:

> On Tue, Dec 16, 2025 at 1:15 AM Ajit Awekar <ajitpostgres@gmail.com>
> wrote:
> > >What I meant that we can already implement a background process that
> > >watches active (oauth) connections, and either:
> >
> > >Revalidates tokens periodically using introspection APIs
> >
> > +1 as this will  offload validation logic to a dedicated background
> process.
>
> Is the hope that batching validation will make things more efficient,
> or is there another goal to using a background process? You still have
> to communicate back to each backend.
>
> --Jacob
>