> On 17 Jun 2024, at 19:56, Andres Freund <andres@anarazel.de> wrote:
> On 2024-06-17 19:51:45 +0200, Daniel Gustafsson wrote:
>> Changing the default of the ecdh GUC would perhaps be doable?
>
> I was wondering whether we could change the default so that it accepts both
> x25519 and secp256r1. Unfortunately that seems to requires changing what we
> use to set the parameter...
Right. The patch in https://commitfest.postgresql.org/48/5025/ does allow for
accepting both but that's a different discussion.
Changing, and backpatching, the default to at least keep new installations from
extra roundtrips doesn't seem that far off in terms of scope from what
860fe27ee1e2 backpatched. Maybe it can be an option.
>> Amending the documentation is the one thing we certainly can do but 99.9% of
>> affected users won't know they are affected so won't look for that section.
>
> Yea. It's also possible that some other bindings changed their default to
> match ours...
There is that possibility, though I think we would've heard something about
that by now if that had happened.
--
Daniel Gustafsson
