Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitf77becb

Browse files
committed
revert "warn of SECURITY DEFINER schemas for non-sql_body funcs"
doc revert of commit1703726. Change was applied to irrelevantbranches, and was not detailed enough to be helpful in relevantbranches.Reported-by: Peter Eisentraut, Noah MischDiscussion:https://postgr.es/m/a2dc9de4-24fc-3222-87d3-0def8057d7d8@enterprisedb.comBackpatch-through: 10
1 parent0937f6d commitf77becb

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

‎doc/src/sgml/ref/create_function.sgml

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -779,10 +779,7 @@ SELECT * FROM dup(42);
779779
<para>
780780
Because a <literal>SECURITY DEFINER</literal> function is executed
781781
with the privileges of the user that owns it, care is needed to
782-
ensure that the function cannot be misused. This is particularly
783-
important for non-<replaceable>sql_body</replaceable> functions because
784-
their function bodies are evaluated at run-time, not creation time.
785-
For security,
782+
ensure that the function cannot be misused. For security,
786783
<xref linkend="guc-search-path"/> should be set to exclude any schemas
787784
writable by untrusted users. This prevents
788785
malicious users from creating objects (e.g., tables, functions, and

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp