Re: Periodic authorization expiration checks using GoAway message
| От | Ajit Awekar |
|---|---|
| Тема | Re: Periodic authorization expiration checks using GoAway message |
| Дата | |
| Msg-id | CAER375PhPdkcapQBUx4kHw82KS1LtTfBgvZ_EpOYqK0n1s5Gpw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Periodic authorization expiration checks using GoAway message (Jacob Champion <jacob.champion@enterprisedb.com>) |
| Ответы |
Re: Periodic authorization expiration checks using GoAway message
|
| Список | 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
В списке pgsql-hackers по дате отправления: