| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | 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-12 14:55:23 |
| Message-ID: | cf349b4e-aa59-46af-a3ec-73157cb37116@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.02.25 02:56, Jacob Champion wrote:
> On Fri, Feb 7, 2025 at 12:12 PM Daniel Gustafsson<daniel(at)yesql(dot)se> wrote:
>> Is it really enough to do this at build time? A very small percentage of users
>> running this will also be building their own libpq so the warning is lost on
>> them. That being said, I'm not entirely sure what else we could do (bleeping a
>> warning every time is clearly not userfriendly) so maybe this is a TODO in the
>> code?
> I've added a TODO back. At the moment, I don't have any good ideas; if
> the user isn't building libpq, they're not going to be able to take
> action on the warning anyway, and for many use cases they're probably
> not going to care.
This just depends on how people have built their libcurl, right?
Do we have any information whether the async-dns-free build is a common
configuration?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2025-02-12 14:59:08 | Re: Parallel CREATE INDEX for GIN indexes |
| Previous Message | Andres Freund | 2025-02-12 14:49:35 | Re: Adding NetBSD and OpenBSD to Postgres CI |