Re: doc: Improve description of io_combine_limit and io_max_combine_limit GUCs - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: doc: Improve description of io_combine_limit and io_max_combine_limit GUCs
Date
Msg-id CAHGQGwEMcMQL7uPS=Q4SfBpuvXYNUwSNgq5e9G0SaPAbng2LBg@mail.gmail.com
Whole thread Raw
In response to Re: doc: Improve description of io_combine_limit and io_max_combine_limit GUCs  (Karina Litskevich <litskevichkarina@gmail.com>)
List pgsql-hackers
On Wed, Nov 5, 2025 at 10:59 PM Karina Litskevich
<litskevichkarina@gmail.com> wrote:
>  * trace_connection_negotiation
>    It is not documented at all. Should it be fixed?

Since other developer parameters like trace_* are already documented,
it seems good to also add trace_connection_negotiation to the docs.
I noticed that a patch for this was already proposed in [1], so it might be
better to revive that thread and review it there.

[1] https://postgr.es/m/CABV9wwPMuKfPf_u36hZmYmbnyZ9e8QvjSCO=EfeyrU+c+=xehA@mail.gmail.com


> I'm attaching these changes as a separate patch just in case. You can
> squash them if you like. Not sure what to do with the commitfest entry.
> Should I change it back to Needs review?

Thanks for the patches! I've pushed them and marked the CF entry as "Committed".

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: Kirill Reshke
Date:
Subject: Re: transformJsonFuncExpr pathspec cache lookup failed
Next
From: Michael Paquier
Date:
Subject: Re: Extended Statistics set/restore/clear functions.