| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Reorder min/max_protocol_version descriptions in libpq documentation |
| Date: | 2025-06-17 16:34:46 |
| Message-ID: | CAGECzQQ2MgUTsUAHESLhW47wA-S3V9vuBzUcP6qRfBY12xGMdA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2025-06-17 21:53:28 | Re: Clarify VACUUM FULL exclusion in total_vacuum_time docs |
| Previous Message | Fujii Masao | 2025-06-17 16:32:11 | Reorder min/max_protocol_version descriptions in libpq documentation |