Horton

Thread

Commits

  1. doc: Use "integer" for some I/O worker GUC type descriptions

  2. doc: Correct context description for some JIT support GUCs

  1. Two small doc fixes for config.sgml

    Fujii Masao <masao.fujii@gmail.com> — 2026-04-20T10:02:52Z

    Hi,

I found two small issues in config.sgml and attached patches for both.

#1
The documentation for jit_debugging_support and jit_profiling_support says
these parameters can only be set at server start. However, both use
the PGC_SU_BACKEND context, which means they can be set at session start
by superusers or users with the appropriate SET privilege, but cannot be
changed within an active session. So, these descriptions should be corrected.
This fix should be backpatched to all supported versions.

#2
config.sgml describes the io_max_workers, io_worker_idle_timeout,
and io_worker_launch_interval GUCs as type "int". Elsewhere, config.sgml
consistently uses "integer" for this type. So those descriptions should be
updated to use "integer" for consistency.

Regards,

-- 
Fujii Masao

  2. Re: Two small doc fixes for config.sgml

    Daniel Gustafsson <daniel@yesql.se> — 2026-04-20T10:13:00Z

    > On 20 Apr 2026, at 12:02, Fujii Masao <masao.fujii@gmail.com> wrote:

> I found two small issues in config.sgml and attached patches for both.

Both fixes LGTM, confirmed that no other <type>int</type> exist (and double
checked if we had any bool/boolean but all seem to use boolean).

--
Daniel Gustafsson

  3. Re: Two small doc fixes for config.sgml

    Fujii Masao <masao.fujii@gmail.com> — 2026-04-20T23:52:17Z

    On Mon, Apr 20, 2026 at 7:13 PM Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 20 Apr 2026, at 12:02, Fujii Masao <masao.fujii@gmail.com> wrote:
>
> > I found two small issues in config.sgml and attached patches for both.
>
> Both fixes LGTM, confirmed that no other <type>int</type> exist (and double
> checked if we had any bool/boolean but all seem to use boolean).

Thanks for the review! I've pushed the patches.

Regards,

-- 
Fujii Masao