1 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.16. Customized Options</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><link rel="prev" href="runtime-config-preset.html" title="19.15. Preset Options" /><link rel="next" href="runtime-config-developer.html" title="19.17. Developer Options" /></head><body id="docContent" class="container-fluid col-10"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">19.16. Customized Options</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="runtime-config-preset.html" title="19.15. Preset Options">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="runtime-config.html" title="Chapter 19. Server Configuration">Up</a></td><th width="60%" align="center">Chapter 19. Server Configuration</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 18.0 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="runtime-config-developer.html" title="19.17. Developer Options">Next</a></td></tr></table><hr /></div><div class="sect1" id="RUNTIME-CONFIG-CUSTOM"><div class="titlepage"><div><div><h2 class="title" style="clear: both">19.16. Customized Options <a href="#RUNTIME-CONFIG-CUSTOM" class="id_link">#</a></h2></div></div></div><p>
3 This feature was designed to allow parameters not normally known to
4 <span class="productname">PostgreSQL</span> to be added by add-on modules
5 (such as procedural languages). This allows extension modules to be
6 configured in the standard ways.
8 Custom options have two-part names: an extension name, then a dot, then
9 the parameter name proper, much like qualified names in SQL. An example
10 is <code class="literal">plpgsql.variable_conflict</code>.
12 Because custom options may need to be set in processes that have not
13 loaded the relevant extension module, <span class="productname">PostgreSQL</span>
14 will accept a setting for any two-part parameter name. Such variables
15 are treated as placeholders and have no function until the module that
16 defines them is loaded. When an extension module is loaded, it will add
17 its variable definitions and convert any placeholder values according to
18 those definitions. If there are any unrecognized placeholders
19 that begin with its extension name, warnings are issued and those
20 placeholders are removed.
21 </p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="runtime-config-preset.html" title="19.15. Preset Options">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="runtime-config.html" title="Chapter 19. Server Configuration">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="runtime-config-developer.html" title="19.17. Developer Options">Next</a></td></tr><tr><td width="40%" align="left" valign="top">19.15. Preset Options </td><td width="20%" align="center"><a accesskey="h" href="index.html" title="PostgreSQL 18.0 Documentation">Home</a></td><td width="40%" align="right" valign="top"> 19.17. Developer Options</td></tr></table></div></body></html>