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

From Karina Litskevich
Subject Re: doc: Improve description of io_combine_limit and io_max_combine_limit GUCs
Date
Msg-id CACiT8iaqKEm1KLajCBDinA+nvLxLABX04S4YR=C4oU9Zz4cm+Q@mail.gmail.com
Whole thread Raw
In response to Re: doc: Improve description of io_combine_limit and io_max_combine_limit GUCs  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Thu, Oct 30, 2025 at 4:31 PM Fujii Masao <masao.fujii@gmail.com> wrote:
>
> I also noticed another issue in the io_max_combine_limit docs.
> Since its context is PGC_POSTMASTER, shouldn't the following
> description be updated to say "This parameter can only be set at server start"?
>
>          This parameter can only be set in
>          the <filename>postgresql.conf</filename> file or on the server
>          command line.
>

Nice catch! I am going to check if there are other GUCs with
PGC_POSTMASTER and wrong documentation. I'll come back with an
updated version of the patch.

Best regards,
Karina Litskevich
Postgres Professional: http://postgrespro.com/



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Next
From: Tom Lane
Date:
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()