doc: Correct context description for some JIT support GUCs

The documentation for jit_debugging_support and jit_profiling_support
previously stated that these parameters can only be set at server start.

However, both parameters use the PGC_SU_BACKEND context, meaning they
can be set at session start by superusers, but cannot be changed within
an active session.

This commit updates the documentation to reflect the actual behavior.

Backpatch to all supported versions.

Author: Fujii Masao <masao.fujii@gmail.com>
Reviewed-by: Daniel Gustafsson <daniel@yesql.se>
Discussion: https://postgr.es/m/CAHGQGwEpMDpB-K8SSUVRRHg6L6z3pLAkekd9aviOS=ns0EC=+Q@mail.gmail.com
Backpatch-through: 14
This commit is contained in:
Fujii Masao 2026-04-21 08:45:45 +09:00
parent 0a26194683
commit f33874c3a9

View file

@ -10978,7 +10978,8 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
If LLVM has the required functionality, register generated functions
with <productname>GDB</productname>. This makes debugging easier.
The default setting is <literal>off</literal>.
This parameter can only be set at server start.
Only superusers can change this parameter at session start,
and it cannot be changed at all within a session.
</para>
</listitem>
</varlistentry>
@ -11028,7 +11029,8 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
This writes out files to <filename>~/.debug/jit/</filename>; the
user is responsible for performing cleanup when desired.
The default setting is <literal>off</literal>.
This parameter can only be set at server start.
Only superusers can change this parameter at session start,
and it cannot be changed at all within a session.
</para>
</listitem>
</varlistentry>