Doc: update documentation of check_function_bodies.
Adjust docs and description string to note that check_function_bodies applies to procedures too. (In hindsight it should have been named check_routine_bodies, but it seems too late for that now.) Daniel Westermann Discussion: https://postgr.es/m/GV0P278MB04834A9EB9A74B036DC7CE49D2739@GV0P278MB0483.CHEP278.PROD.OUTLOOK.COM
This commit is contained in:
parent
152d33bcce
commit
07b76833b1
|
@ -8415,10 +8415,12 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
This parameter is normally on. When set to <literal>off</literal>, it
|
This parameter is normally on. When set to <literal>off</literal>, it
|
||||||
disables validation of the function body string during <xref
|
disables validation of the routine body string during <xref
|
||||||
linkend="sql-createfunction"/>. Disabling validation avoids side
|
linkend="sql-createfunction"/> and <xref
|
||||||
effects of the validation process and avoids false positives due
|
linkend="sql-createprocedure"/>. Disabling validation avoids side
|
||||||
to problems such as forward references. Set this parameter
|
effects of the validation process, in particular preventing false
|
||||||
|
positives due to problems such as forward references.
|
||||||
|
Set this parameter
|
||||||
to <literal>off</literal> before loading functions on behalf of other
|
to <literal>off</literal> before loading functions on behalf of other
|
||||||
users; <application>pg_dump</application> does so automatically.
|
users; <application>pg_dump</application> does so automatically.
|
||||||
</para>
|
</para>
|
||||||
|
@ -9954,7 +9956,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
|
||||||
When set to <literal>on</literal>, which is the default,
|
When set to <literal>on</literal>, which is the default,
|
||||||
<productname>PostgreSQL</productname> will automatically remove
|
<productname>PostgreSQL</productname> will automatically remove
|
||||||
temporary files after a backend crash. If disabled, the files will be
|
temporary files after a backend crash. If disabled, the files will be
|
||||||
retained and may be used for debugging, for example. Repeated crashes
|
retained and may be used for debugging, for example. Repeated crashes
|
||||||
may however result in accumulation of useless files.
|
may however result in accumulation of useless files.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
|
@ -1759,7 +1759,7 @@ static struct config_bool ConfigureNamesBool[] =
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
{"check_function_bodies", PGC_USERSET, CLIENT_CONN_STATEMENT,
|
{"check_function_bodies", PGC_USERSET, CLIENT_CONN_STATEMENT,
|
||||||
gettext_noop("Check function bodies during CREATE FUNCTION."),
|
gettext_noop("Check routine bodies during CREATE FUNCTION and CREATE PROCEDURE."),
|
||||||
NULL
|
NULL
|
||||||
},
|
},
|
||||||
&check_function_bodies,
|
&check_function_bodies,
|
||||||
|
|
Loading…
Reference in New Issue