The corresponding functions set_config and current_setting were
mostly not hyperlinked. Clarify their descriptions a tad, too.
Discussion: https://postgr.es/m/
161183356250.4077.
687338658090583892@wrigleys.postgresql.org
The command allows inspection of the
- current value of all parameters. The corresponding function is
- current_setting(setting_name text).
+ current value of any parameter. The corresponding SQL function is
+ current_setting(setting_name text)
+ (see ).
The command allows modification of the
current value of those parameters that can be set locally to a
session; it has no effect on other sessions.
- The corresponding function is
- set_config(setting_name, new_value, is_local).
+ The corresponding SQL function is
+ set_config(setting_name, new_value, is_local)
+ (see ).
setting
setting_name. If there is no such
setting, current_setting throws an error
unless
missing_ok is supplied and
- is true. This function corresponds to
+ is true (in which case NULL is returned).
+ This function corresponds to
current_setting('datestyle')
Sets the parameter
setting_name
to
new_value, and returns that value.
If
is_local is
true, the new
- value will only apply for the current transaction. If you want the new
- value to apply for the current session, use false
- instead. This function corresponds to the SQL
- command SET>.
+ value will only apply during the current transaction. If you want the
+ new value to apply for the rest of the current session,
+ use false instead. This function corresponds to
+ the SQL command >.
set_config('log_statement_stats', 'off', false)
The function set_config provides equivalent
- functionality; see .
+ functionality; see -set"/>.
Also, it is possible to UPDATE the
pg_settings
system view to perform the equivalent of SET.
The function current_setting produces
- equivalent output; see .
+ equivalent output; see -set"/>.
Also, the
pg_settings
system view produces the same information.