2 19.16. Customized Options #
4 This feature was designed to allow parameters not normally known to
5 PostgreSQL to be added by add-on modules (such as procedural
6 languages). This allows extension modules to be configured in the
9 Custom options have two-part names: an extension name, then a dot, then
10 the parameter name proper, much like qualified names in SQL. An example
11 is plpgsql.variable_conflict.
13 Because custom options may need to be set in processes that have not
14 loaded the relevant extension module, PostgreSQL will accept a setting
15 for any two-part parameter name. Such variables are treated as
16 placeholders and have no function until the module that defines them is
17 loaded. When an extension module is loaded, it will add its variable
18 definitions and convert any placeholder values according to those
19 definitions. If there are any unrecognized placeholders that begin with
20 its extension name, warnings are issued and those placeholders are