Re: Add ssl_(supported|shared)_groups to sslinfo

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add ssl_(supported|shared)_groups to sslinfo
Date: 2026-02-23 16:48:02
Message-ID: CAOYmi+nkT7rkbNd6que0wtz=epOikgBKSDR88DQ=cyNJwiUw8Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 23, 2026 at 6:32 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> +CREATE FUNCTION ssl_shared_groups() RETURNS text

I don't feel strongly about this, so feel free to disregard: Is there
a reason this API is focusing on the shared group list as opposed to
the actual negotiated group in use? The latter seems more widely
useful to me, and it'd match up with ssl_cipher(). (Or maybe we
already have the negotiated group somewhere and I just never noticed?)

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-02-23 17:07:21 Re: [PATCH] Support reading large objects with pg_read_all_data
Previous Message Álvaro Herrera 2026-02-23 16:47:46 Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists