Re: [PoC] Federated Authn/z with OAUTHBEARER

From: Wolfgang Walther <walther(at)technowledgy(dot)de>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Christoph Berg <myon(at)debian(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Antonin Houska <ah(at)cybertec(dot)at>
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER
Date: 2025-04-08 17:10:07
Message-ID: 214ec3cc-7531-4360-8103-663581d2149f@technowledgy.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jacob Champion:
>> However, if the other deps are considered problematic as well, then the
>> ship has already sailed, and there is not point for a special case here
>> anymore.
> I think this line of argument is unlikely to find traction. Upthread
> there were people asking if we could maybe split out other
> possibly-unused dependencies in the future, like Kerberos.

Well, yes, that's kind of what I'm saying. There shouldn't be a special
case for cURL, but those other deps should be handled equally as well.

And if that means making libpq modular at run-time, then this should be
planned and built with all deps, and other use-cases (like static
linking) in mind - and not like it is right now.

Best,

Wolfgang

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2025-04-08 17:12:48 Re: Finalizing read stream users' flag choices
Previous Message Tom Lane 2025-04-08 17:07:09 Re: Horribly slow pg_upgrade performance with many Large Objects