From e723c3bd6ea3b4502366c28f9c28d3bfb8fc2124 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 28 Sep 2022 13:05:20 -0400 Subject: [PATCH] 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 5762d973090..74866e8b353 100644 --- a/doc/src/sgml/ref/create_function.sgml +++ b/doc/src/sgml/ref/create_function.sgml @@ -715,10 +715,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 -- 2.39.5