doc: Add note about pg_settings and customized options into catalogs.sgml.

The pg_settings view does not display customized options until
the extension module that defines them has been loaded. This commit
add the note about that behavior, into the docs.

Author: John Naylor
Reviewed-by: Tom Lane, Fujii Masao
Discussion: https://postgr.es/m/CAFBsxsGsBZsG=cLM0Op5HFb2Ks6SzJrOc_eRO_jcKSNuqFRKnQ@mail.gmail.com
This commit is contained in:
Fujii Masao 2020-11-09 15:10:26 +09:00
parent 3636efa119
commit ef60de67eb
1 changed files with 8 additions and 4 deletions

View File

@ -12279,10 +12279,14 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
</para>
<para>
The <structname>pg_settings</structname> view cannot be inserted into or
deleted from, but it can be updated. An <command>UPDATE</command> applied
to a row of <structname>pg_settings</structname> is equivalent to executing
the <command>SET</command> command on that named
This view does not display <link linkend="runtime-config-custom">customized options</link>
until the extension module that defines them has been loaded.
</para>
<para>
This view cannot be inserted into or deleted from, but it can be updated. An
<command>UPDATE</command> applied to a row of <structname>pg_settings</structname>
is equivalent to executing the <command>SET</command> command on that named
parameter. The change only affects the value used by the current
session. If an <command>UPDATE</command> is issued within a transaction
that is later aborted, the effects of the <command>UPDATE</command> command