database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-29 23:43:17 +03:00
Code Activity

Add GUC to show EXEC_BACKEND state

Browse Source 
There is no straightforward way to determine if a cluster is running
in EXEC_BACKEND mode or not, which is useful for tests to know. This
adds a GUC debug_exec_backend similar to debug_assertions which will
be true when the server is running in EXEC_BACKEND mode.

Author: Daniel Gustafsson <daniel@yesql.se>
Reviewed-by: Chao Li <li.evan.chao@gmail.com>
Reviewed-by: Álvaro Herrera <alvherre@kurilemu.de>
Reviewed-by: Peter Eisentraut <peter@eisentraut.org>
Discussion: https://postgr.es/m/5F301096-921A-427D-8EC1-EBAEC2A35082@yesql.se
This commit is contained in:
Daniel Gustafsson
2025-11-26 14:24:27 +01:00
parent 0f4f45772c
commit b3fe098d33
3 changed files with 31 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
doc/src/sgml/config.sgml
View File

@@ -11833,6 +11833,23 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir'
</listitem>
</varlistentry>
<varlistentry id="guc-debug-exec-backend" xreflabel="debug_exec_backend">
<term><varname>debug_exec_backend</varname> (<type>boolean</type>)
<indexterm>
<primary><varname>debug_exec_backend</varname> configuration parameter</primary>
</indexterm>
</term>
<listitem>
<para>
Reports whether <productname>PostgreSQL</productname> has been built
with <literal>EXEC_BACKEND</literal> enabled. That is the case on
<systemitem class="osname">Windows</systemitem> or if the
macro <symbol>EXEC_BACKEND</symbol> is defined
when <productname>PostgreSQL</productname> is built.
</para>
</listitem>
</varlistentry>
<varlistentry id="guc-huge-pages-status" xreflabel="huge_pages_status">
<term><varname>huge_pages_status</varname> (<type>enum</type>)
<indexterm>