PostgreSQL 10 ← 9.6
← Catalog atlas / pg_file_settings
SYSTEM VIEW · System view
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.
Checked column by column against a PostgreSQL 18.6 instance · Raw measurement record ↗
Columns PostgreSQL 18
pg_file_settingsPostgreSQL 19 beta 3 is a preview snapshot; the structure can still change before release.
| COLUMN | TYPE | DESCRIPTION |
|---|---|---|
sourcefile |
text |
Full path name of the configuration file |
sourceline |
integerDocumented as:int4 |
Line number within the configuration file where the entry appears |
seqno |
integerDocumented as: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 |
booleanDocumented as: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 |
Columns marked "implicit" are not included in SELECT *; some early statistics views are completed from same-version source, and the extra provenance is shown in the column description.
Common system columns 0
System attributes PostgreSQL provides, normally not expanded by SELECT *. Kept separately so they are not mixed in with ordinary columns.
| Columns | Type | attnum |
|---|
Column evolution matrix
Hover a cell for the column typePresentAdded / type or attribute changeRemoved
| COLUMN | 9.0 | 9.1 | 9.2 | 9.3 | 9.4 | 9.5 | 9.6 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sourcefile |
– | – | – | – | – | ||||||||||||
sourceline |
– | – | – | – | – | ||||||||||||
seqno |
– | – | – | – | – | ||||||||||||
name |
– | – | – | – | – | ||||||||||||
setting |
– | – | – | – | – | ||||||||||||
applied |
– | – | – | – | – | ||||||||||||
error |
– | – | – | – | – |
9.0 is the coverage baseline; a column already present in the baseline is not marked as added. The matrix aligns columns by name, so a rename appears as the old column removed and a new column added.
Evolution timeline
Changes between adjacent majorsPostgreSQL 9.6 ← 9.5
PostgreSQL 9.5 ← 9.4Catalog added
Compare any two versions
Pick two versions to see added, removed, and retyped columns. The interactive comparison needs JavaScript; the evolution timeline reads fine without it.