| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Daniel Gustafsson <daniel(at)yesql(dot)se>, rmt(at)lists(dot)postgresql(dot)org, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Subject: | Re: [oauth] Increased CPU usage during device flow with libcurl 8.20.0 |
| Date: | 2026-06-16 20:40:50 |
| Message-ID: | 965822.1781642450@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> Attached as v2-0002, which moves the version check into one of the
> OAuth test executables. (I'll hold 0004 until after REL_19_STABLE is
> branched; it just implements the v1 strategy and reverts 0002.)
> I've tested this against a local Homebrew installation, but if anyone
> who's hit this in the wild has a chance to put 0001-3 through a smoke
> test, that'd be awesome. Barring any objections or bad test results,
> I'll plan to push tomorrow.
I confirm that, with or without 0004, this fixes the oauth_validator
failure on the machine where I saw that.
However ... I don't love the plan of fixing this differently in v19
and v20 just because of feature freeze. Exposing more information
for testing purposes isn't a user-visible feature IMO, so I would
rather we go straight to 0004.
CC'ing the RMT to see if they agree. (I think the rmt@ alias is
not functioning, so cc'ing members directly.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2026-06-16 20:58:04 | Re: [oauth] Increased CPU usage during device flow with libcurl 8.20.0 |
| Previous Message | Zsolt Parragi | 2026-06-16 20:22:06 | Require SSL connection to postgres for oauth |