Re: [PATCH] Clarify that ssl_groups is for any key exchange groups

From: Evan <evansi(dot)dev(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: "Si, Evan" <evsi(at)amazon(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Ewan Young <kdbase(dot)hack(at)gmail(dot)com>
Subject: Re: [PATCH] Clarify that ssl_groups is for any key exchange groups
Date: 2026-06-06 02:45:43
Message-ID: 99d0c7eb-e648-40b0-98c4-1a1ae6255796@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/5/2026 1:22 PM, Daniel Gustafsson wrote:
>> On 4 Jun 2026, at 05:00, Ewan Young <kdbase(dot)hack(at)gmail(dot)com> wrote:
>
>> v2 looks good to me, and I have nothing further.
>
> I have applied the docs portion of this patch to master and REL_18_STABLE, but
> given where we are in the release cycle I don't think the renames qualify as
> fixes during a freeze. Please feel free to register this patch in the upcoming
> commitfest to get the remaining portion into v20. You can add me as a reviewer
> on that entry to make sure it stays on my radar.
>
Thanks! It looks like you found the commitfest entry for it right after
the email.

Otherwise for reference: https://commitfest.postgresql.org/patch/6843/

(Same person, different email.)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-06-06 03:06:00 Re: Fix bug of CHECK constraint enforceability recursion
Previous Message Chao Li 2026-06-06 01:10:46 Re: Prevent remote libpq notices from being sent to clients