| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, rmt(at)lists(dot)postgresql(dot)org, 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-17 15:40:04 |
| Message-ID: | ajK_1G-v2UJmsML9@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[RMT hat]
On Tue, Jun 16, 2026 at 05:02:28PM -0400, Tom Lane wrote:
> Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
>> On Tue, Jun 16, 2026 at 1:40 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
This seems like a reasonable plan to me.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2026-06-17 15:50:57 | Re: [oauth] Increased CPU usage during device flow with libcurl 8.20.0 |
| Previous Message | Tom Lane | 2026-06-17 15:36:23 | Re: [PATCH] Doc: document standard_conforming_strings dump/restore incompatibility |