2 53.8. pg_file_settings #
4 The view pg_file_settings provides a summary of the contents of the
5 server's configuration file(s). A row appears in this view for each
6 “name = value” entry appearing in the files, with annotations
7 indicating whether the value could be applied successfully. Additional
8 row(s) may appear for problems not linked to a “name = value” entry,
9 such as syntax errors in the files.
11 This view is helpful for checking whether planned changes in the
12 configuration files will work, or for diagnosing a previous failure.
13 Note that this view reports on the current contents of the files, not
14 on what was last applied by the server. (The pg_settings view is
15 usually sufficient to determine that.)
17 By default, the pg_file_settings view can be read only by superusers.
19 Table 53.8. pg_file_settings Columns
27 Full path name of the configuration file
31 Line number within the configuration file where the entry appears
35 Order in which the entries are processed (1..n)
39 Configuration parameter name
43 Value to be assigned to the parameter
47 True if the value can be applied successfully
51 If not null, an error message indicating why this entry could not be
54 If the configuration file contains syntax errors or invalid parameter
55 names, the server will not attempt to apply any settings from it, and
56 therefore all the applied fields will read as false. In such a case
57 there will be one or more rows with non-null error fields indicating
58 the problem(s). Otherwise, individual settings will be applied if
59 possible. If an individual setting cannot be applied (e.g., invalid
60 value, or the setting cannot be changed after server start) it will
61 have an appropriate message in the error field. Another way that an
62 entry might have applied = false is that it is overridden by a later
63 entry for the same parameter name; this case is not considered an error
64 so nothing appears in the error field.
66 See Section 19.1 for more information about the various ways to change