Re: [oauth] Increased CPU usage during device flow with libcurl 8.20.0
Melanie Plageman <melanieplageman@gmail.com>
From: Melanie Plageman <melanieplageman@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
Jacob Champion <jacob.champion@enterprisedb.com>, Daniel Gustafsson <daniel@yesql.se>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andrew Dunstan <andrew@dunslane.net>, rmt@lists.postgresql.org, Heikki Linnakangas <hlinnaka@iki.fi>
Date: 2026-06-17T15:50:57Z
Lists: pgsql-hackers
On Wed, Jun 17, 2026 at 11:40 AM Nathan Bossart <nathandbossart@gmail.com> wrote: > > >> Fair enough. If the RMT is okay with this for 19, were you thinking > >> we'd also backpatch that code directly to 18? > > > > Sure. > > This seems like a reasonable plan to me. +1
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