Horton

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

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

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Daniel Gustafsson <daniel@yesql.se>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andrew Dunstan <andrew@dunslane.net>, rmt@lists.postgresql.org, Nathan Bossart <nathandbossart@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>, Melanie Plageman <melanieplageman@gmail.com>
Date: 2026-06-16T21:02:28Z
Lists: pgsql-hackers 
Jacob Champion <jacob.champion@enterprisedb.com> writes:
> On Tue, Jun 16, 2026 at 1:40 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.

> Fair enough. If the RMT is okay with this for 19, were you thinking
> we'd also backpatch that code directly to 18?

Sure.

			regards, tom lane

Commits

  1. oauth: Skip call-count test for libcurl 8.20.0

  2. libpq-oauth: Print libcurl version with OAUTHDEBUG_UNSAFE_TRACE