Database Reference
In-Depth Information
application_name | client | psql
log_timezone | command line | GB
TimeZone | command line | GB
timezone_abbreviations | command line | Default
archive_command | configuration file | (disabled)
archive_mode | configuration file | off
archive_timeout | configuration file | 5
bgwriter_delay | configuration file | 10
checkpoint_timeout | configuration file | 30
log_checkpoints | configuration file | on
log_destination | configuration file | stderr
log_filename | configuration file | log%Y
logging_collector | configuration file | on
log_line_prefix | configuration file | %t[%p]
log_min_messages | configuration file | log
max_prepared_transactions | configuration file | 5
max_standby_delay | configuration file | 90
port | configuration file | 5443
max_stack_depth | environment variable | 2048
work_mem | session | 204800
(29 rows)
('Override' is excluded just for display purposes.)
How it works...
You can see from
pg_settings
which values have non-default values, and what
the source of the current value is.
The
SHOW
command doesn't tell you whether a parameter is set at a non-default value. It just
tells you the value, which isn't much help if you're trying to understand what is set and why.
If the source is a configuration file, then the two columns
sourcefile
and
sourceline
are also set. These can be useful in understanding where the configuration came from.
There's more...
The
setting
column of
pg_settings
shows the current value, though you can also
look at
boot_val
and
reset_val
;
boot-val
, which show the value assigned when the
PostgreSQL database cluster was initialized ("initdb"), while
reset_val
shows the value that
the parameter will return to if you issue the
RESET
command.
Who set that?
max_stack_depth
is an exception because
pg_settings
says it is set by the
environment variable, though it is actually set by
ulimit -s
on Linux/Unix systems.
max_stack_depth
only needs to be set directly on Windows.