From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Reorder min/max_protocol_version descriptions in libpq documentation |
Date: | 2025-06-18 00:21:18 |
Message-ID: | 7dd9ec53-e58c-44fa-b4ef-b92c9b0a6005@oss.nttdata.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 2025/06/18 1:34, Jelte Fennema-Nio wrote:
> On Tue, 17 Jun 2025 at 18:32, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>>
>> Hi,
>>
>> Commit 285613c60a7 added the min_protocol_version and max_protocol_version
>> connection options to libpq. However, their descriptions currently appear
>> in the middle of the unrelated ssl_min_protocol_version and
>> ssl_max_protocol_version entries in libpq.sgml. Is there a reason for
>> this placement?
>
> Not that I can remember, probably because I copied the
> ssl_min_protocol_version section when writing the initial version
> min_protocol_version section.
>
>> To make the documentation more intuitive and easier to navigate,
>> I suggest moving these entries after the SSL-related options.
>> Attached is a patch that does that.
>
> +1
I've pushed the patch. Thanks!
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2025-06-18 05:34:55 | Fix inaccurate mention of index comments in CREATE FOREIGN TABLE docs |
Previous Message | Robert Treat | 2025-06-17 21:53:28 | Re: Clarify VACUUM FULL exclusion in total_vacuum_time docs |