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 parameter is normally on. When set to off, it
- disables validation of the function body string during
- linkend="sql-createfunction"/>. Disabling validation avoids side
- effects of the validation process and avoids false positives due
- to problems such as forward references. Set this parameter
+ disables validation of the routine body string during
+ linkend="sql-createfunction"/> and
+ linkend="sql-createprocedure"/>. Disabling validation avoids side
+ effects of the validation process, in particular preventing false
+ positives due to problems such as forward references.
+ Set this parameter
to off before loading functions on behalf of other
users;
pg_dump does so automatically.
When set to on, which is the default,
PostgreSQL will automatically remove
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.
},
{
{"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
},
&check_function_bodies,