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

diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml
index 35869bf6ba64735533d5f5d11531091dead925b4..7e6d52c7dcf36a1dc59b84e9c6909715e244eb89 100644 (file)
--- a/doc/src/sgml/ref/create_function.sgml
+++ b/doc/src/sgml/ref/create_function.sgml
@@ -779,10 +779,7 @@ SELECT * FROM dup(42);
    
     Because a SECURITY DEFINER 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-sql_body functions because
-    their function bodies are evaluated at run-time, not creation time.
-    For security,
+    ensure that the function cannot be misused.  For security,
      should be set to exclude any schemas
     writable by untrusted users.  This prevents
     malicious users from creating objects (e.g., tables, functions, and