From b3fe098d330ff6a7c23019d66a600072b1d4664d Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson Date: Wed, 26 Nov 2025 14:24:27 +0100 Subject: Add GUC to show EXEC_BACKEND state MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 Reviewed-by: Chao Li Reviewed-by: Álvaro Herrera Reviewed-by: Peter Eisentraut Discussion: https://postgr.es/m/5F301096-921A-427D-8EC1-EBAEC2A35082@yesql.se --- doc/src/sgml/config.sgml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 07ff5873a97..737b90736bf 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -11833,6 +11833,23 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' + + debug_exec_backend (boolean) + + debug_exec_backend configuration parameter + + + + + Reports whether PostgreSQL has been built + with EXEC_BACKEND enabled. That is the case on + Windows or if the + macro EXEC_BACKEND is defined + when PostgreSQL is built. + + + + huge_pages_status (enum) -- cgit v1.2.3