From 17fa3e834f288a2a8f0b3927d3f7f02451126686 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Mon, 20 Mar 2017 22:33:26 -0400
Subject: [PATCH] doc:  clarify that function "ownership" that controls
 permission

It used to say the creation user.

Reported-by: Nathan Wagner
---
 doc/src/sgml/ref/create_function.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml
index e7057789d3..9d0d2f4beb 100644
--- a/doc/src/sgml/ref/create_function.sgml
+++ b/doc/src/sgml/ref/create_function.sgml
@@ -401,7 +401,7 @@ CREATE [ OR REPLACE ] FUNCTION
       is to be executed with the privileges of the user that calls it.
       That is the default.  <literal>SECURITY DEFINER</literal>
       specifies that the function is to be executed with the
-      privileges of the user that created it.
+      privileges of the user that owns it.
      </para>
 
      <para>
@@ -747,7 +747,7 @@ SELECT * FROM dup(42);
 
    <para>
     Because a <literal>SECURITY DEFINER</literal> function is executed
-    with the privileges of the user that created it, care is needed to
+    with the privileges of the user that owns it, care is needed to
     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
-- 
2.40.0