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

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add ssl_(supported|shared)_groups to sslinfo
Date: 2026-02-23 15:26:44
Message-ID: eeljgor4gt23ylwihz4jkh7j3xur7xrvky6dou3vwewkj5xotp@o3l7zmq5oalq
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Mon, Feb 23, 2026 at 03:32:02PM +0100, Daniel Gustafsson wrote:
> +PG_FUNCTION_INFO_V1(ssl_supported_groups);
> +Datum
> +ssl_supported_groups(PG_FUNCTION_ARGS)
> The supported groups is sent as a TLS extension, and we already have
> ssl_extension_info() for listing extension values. Shouldn't this be a part of
> that function for consistency?

Good point, thanks. I'll move the functionality in there.

> --- /dev/null
> +++ b/contrib/sslinfo/sslinfo--1.3.sql
> @@ -0,0 +1,56 @@
> +/* contrib/sslinfo/sslinfo--1.3.sql */
> No need to spin a new 1.3 file, the upgrade file from 1.2 to 1.3 is sufficient
> since the extension machinery will play the files in order to reach 1.3.
>
>
> +CREATE FUNCTION ssl_shared_groups() RETURNS text
> Why not return this as text[] rather than a delimited string?

No particular reason, but I see the point -- going to change it to text[].

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-02-23 15:27:17 Re: refactor architecture-specific popcount code
Previous Message David Geier 2026-02-23 15:24:57 Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?