Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit b6fe152

Browse files
committed
doc: warn of SECURITY DEFINER schemas for non-sql_body functions
Non-sql_body functions are evaluated at runtime. Reported-by: Erki Eessaar Discussion: https://postgr.es/m/AM9PR01MB8268BF5E74E119828251FD34FE409@AM9PR01MB8268.eurprd01.prod.exchangelabs.com Backpatch-through: 10
1 parent c7dbe90 commit b6fe152

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

doc/src/sgml/ref/create_function.sgml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -729,7 +729,10 @@ SELECT * FROM dup(42);
729729
<para>
730730
Because a <literal>SECURITY DEFINER</literal> function is executed
731731
with the privileges of the user that owns it, care is needed to
732-
ensure that the function cannot be misused. For security,
732+
ensure that the function cannot be misused. This is particularly
733+
important for non-<replaceable>sql_body</replaceable> functions because
734+
their function bodies are evaluated at run-time, not creation time.
735+
For security,
733736
<xref linkend="guc-search-path"/> should be set to exclude any schemas
734737
writable by untrusted users. This prevents
735738
malicious users from creating objects (e.g., tables, functions, and

0 commit comments

Comments
 (0)