From 0f3f34f098baf2aee41b8de7feb4b05add644d7d Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 28 May 2004 16:37:11 +0000 Subject: [PATCH] Fix minor error in comment. --- src/backend/catalog/aclchk.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/backend/catalog/aclchk.c b/src/backend/catalog/aclchk.c index 4ab6717c7c..3aaabf1b99 100644 --- a/src/backend/catalog/aclchk.c +++ b/src/backend/catalog/aclchk.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/catalog/aclchk.c,v 1.101 2004/05/28 16:17:14 tgl Exp $ + * $PostgreSQL: pgsql/src/backend/catalog/aclchk.c,v 1.102 2004/05/28 16:37:11 tgl Exp $ * * NOTES * See acl.h. @@ -1355,9 +1355,10 @@ pg_namespace_aclmask(Oid nsp_oid, AclId userid, * * This may seem redundant given the check in InitTempTableNamespace, * but it really isn't since current user ID may have changed since then. - * The upshot of this behavior is that a SECURITY INVOKER function can + * The upshot of this behavior is that a SECURITY DEFINER function can * create temp tables that can then be accessed (if permission is granted) - * by code that doesn't have permissions to create temp tables. + * by code in the same session that doesn't have permissions to create + * temp tables. * * XXX Would it be safe to ereport a special error message as * InitTempTableNamespace does? Returning zero here means we'll get a -- 2.40.0