| From: | Karina Litskevich <litskevichkarina(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: doc: Improve description of io_combine_limit and io_max_combine_limit GUCs |
| Date: | 2025-10-31 14:45:07 |
| Message-ID: | CACiT8iaqKEm1KLajCBDinA+nvLxLABX04S4YR=C4oU9Zz4cm+Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 30, 2025 at 4:31 PM Fujii Masao <masao(dot)fujii(at)gmail(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-10-31 15:17:11 | Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats() |
| Previous Message | Nathan Bossart | 2025-10-31 14:09:36 | Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats() |