From 6eb9c5a5657d1fe77b55cc261450f3538d35a94d Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:19:15 +0200 Subject: Adding upstream version 13.4. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/view-pg-file-settings.html | 77 ++++++++++++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 doc/src/sgml/html/view-pg-file-settings.html (limited to 'doc/src/sgml/html/view-pg-file-settings.html') diff --git a/doc/src/sgml/html/view-pg-file-settings.html b/doc/src/sgml/html/view-pg-file-settings.html new file mode 100644 index 0000000..037f82e --- /dev/null +++ b/doc/src/sgml/html/view-pg-file-settings.html @@ -0,0 +1,77 @@ + +51.69. pg_file_settings

51.69. pg_file_settings

+ The view pg_file_settings provides a summary of + the contents of the server's configuration file(s). A row appears in + this view for each name = value entry appearing in the files, + with annotations indicating whether the value could be applied + successfully. Additional row(s) may appear for problems not linked to + a name = value entry, such as syntax errors in the files. +

+ This view is helpful for checking whether planned changes in the + configuration files will work, or for diagnosing a previous failure. + Note that this view reports on the current contents of the + files, not on what was last applied by the server. (The + pg_settings + view is usually sufficient to determine that.) +

+ By default, the pg_file_settings view can be read + only by superusers. +

Table 51.70. pg_file_settings Columns

+ Column Type +

+

+ Description +

+ sourcefile text +

+

+ Full path name of the configuration file +

+ sourceline int4 +

+

+ Line number within the configuration file where the entry appears +

+ seqno int4 +

+

+ Order in which the entries are processed (1..n) +

+ name text +

+

+ Configuration parameter name +

+ setting text +

+

+ Value to be assigned to the parameter +

+ applied bool +

+

+ True if the value can be applied successfully +

+ error text +

+

+ If not null, an error message indicating why this entry could + not be applied +


+ If the configuration file contains syntax errors or invalid parameter + names, the server will not attempt to apply any settings from it, and + therefore all the applied fields will read as false. + In such a case there will be one or more rows with + non-null error fields indicating the + problem(s). Otherwise, individual settings will be applied if possible. + If an individual setting cannot be applied (e.g., invalid value, or the + setting cannot be changed after server start) it will have an appropriate + message in the error field. Another way that + an entry might have applied = false is that it is + overridden by a later entry for the same parameter name; this case is not + considered an error so nothing appears in + the error field. +

+ See Section 19.1 for more information about the various + ways to change run-time parameters. +

\ No newline at end of file -- cgit v1.2.3