Here is a patch with the proposed wording.
From 7fce0073f8a53b3e9ba84fa10fbc7b8efef36e97 Mon Sep 17 00:00:00 2001 From: benoit <benoit.lobr...@dalibo.com> Date: Mon, 22 Aug 2022 12:00:46 +0200 Subject: [PATCH] basic_archive parameter visibility doc patch
Module parameters are only visible from the pg_settings view once the module is loaded. Since an archive module is loaded by the archiver process, the parameters are never visible from the view. This patch adds a note bout this in the pg_settings system view documentation. --- doc/src/sgml/system-views.sgml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/system-views.sgml b/doc/src/sgml/system-views.sgml index 9728039e71..92aad11c71 100644 --- a/doc/src/sgml/system-views.sgml +++ b/doc/src/sgml/system-views.sgml @@ -3275,7 +3275,13 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx <para> This view does not display <link linkend="runtime-config-custom">customized options</link> - until the extension module that defines them has been loaded. + until the extension module that defines them has been loaded by the backend + process executing the query (e.g., via shared_preload_libraries, the + <command>LOAD</command> command, or a call to a user-defined C function). + For example, since the archive_library is only loaded by the archiver + process, this view will not display any customized options defined by + archive modules unless special action is taken to load them into the backend + process executing the query. </para> <para> -- 2.37.1