Re: Setting min/max TLS protocol in clientside libpq - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Setting min/max TLS protocol in clientside libpq
Date
Msg-id 1845A083-BA45-4881-B1A0-B6B25026E1DE@yesql.se
Whole thread Raw
In response to Re: Setting min/max TLS protocol in clientside libpq  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Setting min/max TLS protocol in clientside libpq  (Michael Paquier <michael@paquier.xyz>)
Re: Setting min/max TLS protocol in clientside libpq  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
> On 24 Apr 2020, at 12:56, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
>
> Can we reconsider whether we really want to name the new settings like "sslminprotocolversion", or whether we could
addsome underscores, both for readability and for consistency with the server-side options? 

That was brought up by Michael in the thread, but none of us followed up on it
it seems.  The current name was chosen to be consistent with the already
existing ssl* client-side settings, but I don't really have strong opinions on
if that makes sense or not.  Perhaps use ssl_m{in|max}_protocolversion to make
it more readable?

The attached renames the userfacing setting, but keeps the environment variable
without underscores as most settings have env vars without underscores.

cheers ./daniel


Attachment

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: proposal - plpgsql - all plpgsql auto variables should be constant
Next
From: Robert Haas
Date:
Subject: Re: backup manifests