Re: [PoC] Federated Authn/z with OAUTHBEARER

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Antonin Houska <ah(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER
Date: 2025-02-21 21:18:01
Message-ID: FA245325-A552-4302-BCF6-4AFF494E3B0D@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 21 Feb 2025, at 18:18, Andres Freund <andres(at)anarazel(dot)de> wrote:

> One question about interruptability. The docs say:
> ....

> Afaict the only real way to do safely across platforms is to never call
> blocking functions, e.g. by using non-blocking sockets and waiting for
> readiness using latches.

Fair point, we'll work on a proposed new wording for this.

> And a second one about supporting !CURL_VERSION_ASYNCHDNS:
>
> Is it a good idea to support that?

We could block building instead of the current warning, but that's at best what
we can do. I spent some time skimming over package definitions for the major
distributions ans OS's and couldn't find any that use sync dns.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2025-02-21 21:20:08 Re: explain analyze rows=%.0f
Previous Message Andrew Dunstan 2025-02-21 21:11:54 Re: TAP test started using meson, can get a tcp port already used by another test.