Re: [oauth] Increased CPU usage during device flow with libcurl 8.20.0

Jacob Champion <jacob.champion@enterprisedb.com>

From: Jacob Champion <jacob.champion@enterprisedb.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andrew Dunstan <andrew@dunslane.net>, Daniel Gustafsson <daniel@yesql.se>

Date: 2026-06-16T19:46:31Z

Lists: pgsql-hackers

Attachments

v2-0001-oauth_validator-Print-captured-stderr-after-call-.patch (application/octet-stream) patch v2-0001
v2-0002-oauth_hook_client-Print-the-linked-libcurl-versio.patch (application/octet-stream) patch v2-0002
v2-0003-oauth-Skip-call-count-test-for-libcurl-8.20.0.patch (application/octet-stream) patch v2-0003
v2-0004-libpq-oauth-Print-libcurl-version-with-OAUTHDEBUG.patch (application/octet-stream) patch v2-0004

On Mon, Jun 15, 2026 at 3:56 PM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
> I need to switch to a different context for today, but tomorrow I'll
> try to find a solution that touches only the test code.

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.

Thanks!
--Jacob

Commits

oauth: Skip call-count test for libcurl 8.20.0
- c5c35fd7c55c 18 (unreleased) landed
- fd5ea2e9e37c 19 (unreleased) landed
libpq-oauth: Print libcurl version with OAUTHDEBUG_UNSAFE_TRACE
- 357e4d64f871 18 (unreleased) landed
- 4bd477dcc619 19 (unreleased) landed