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 e71ca092c623dc6b7947b9a4267eaf298aac8746..01b7d18f9ecc30e450086cfdf7dc2ad6ea2eb98f 100644 (file)
--- a/doc/src/sgml/ref/create_function.sgml
+++ b/doc/src/sgml/ref/create_function.sgml
@@ -729,10 +729,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