postgres.git / summary / log / commit / refs

commit    bbdc1d2334e63f761e4baf37ca3243f66f56f6be
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Wed Sep 28 17:05:20 2022 +0000

    revert "warn of SECURITY DEFINER schemas for non-sql_body funcs"
    
    doc revert of commit 1703726488.  Change was applied to irrelevant
    branches, and was not detailed enough to be helpful in relevant
    branches.
    
    Reported-by: Peter Eisentraut, Noah Misch
    
    Discussion: https://postgr.es/m/a2dc9de4-24fc-3222-87d3-0def8057d7d8@enterprisedb.com
    
    Backpatch-through: 10


 doc/src/sgml/ref/create_function.sgml | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml
index 35869bf6ba6..7e6d52c7dcf 100644
--- a/doc/src/sgml/ref/create_function.sgml
+++ b/doc/src/sgml/ref/create_function.sgml
@@ -779,10 +779,7 @@ SELECT * FROM dup(42);
    <para>
     Because a <literal>SECURITY DEFINER</literal> function is executed
     with the privileges of the user that owns it, care is needed to
-    ensure that the function cannot be misused.  This is particularly
-    important for non-<replaceable>sql_body</replaceable> functions because
-    their function bodies are evaluated at run-time, not creation time.
-    For security,
+    ensure that the function cannot be misused.  For security,
     <xref linkend="guc-search-path"/> should be set to exclude any schemas
     writable by untrusted users.  This prevents
     malicious users from creating objects (e.g., tables, functions, and


[parent: f1e7f25b5aef]