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

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 5fb9dca4258cb35b88e89dc6311f33ff0c8e42ad..569841398b4ed3038ca9e9424430b7d6d3710d9f 100644 (file)
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -12279,10 +12279,14 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
   
 
   
-   The pg_settings view cannot be inserted into or
-   deleted from, but it can be updated.  An UPDATE applied
-   to a row of pg_settings is equivalent to executing
-   the SET command on that named
+   This view does not display customized options
+   until the extension module that defines them has been loaded.
+  
+
+  
+   This view cannot be inserted into or deleted from, but it can be updated.  An
+   UPDATE applied to a row of pg_settings
+   is equivalent to executing the SET command on that named
    parameter. The change only affects the value used by the current
    session. If an UPDATE is issued within a transaction
    that is later aborted, the effects of the UPDATE command