|
8 | 8 | * |
9 | 9 | * |
10 | 10 | * IDENTIFICATION |
11 | | - * $PostgreSQL: pgsql/src/backend/catalog/aclchk.c,v 1.101 2004/05/28 16:17:14 tgl Exp $ |
| 11 | + * $PostgreSQL: pgsql/src/backend/catalog/aclchk.c,v 1.102 2004/05/28 16:37:11 tgl Exp $ |
12 | 12 | * |
13 | 13 | * NOTES |
14 | 14 | * See acl.h. |
@@ -1355,9 +1355,10 @@ pg_namespace_aclmask(Oid nsp_oid, AclId userid, |
1355 | 1355 | * |
1356 | 1356 | * This may seem redundant given the check in InitTempTableNamespace, |
1357 | 1357 | * but it really isn't since current user ID may have changed since then. |
1358 | | - * The upshot of this behavior is that a SECURITYINVOKER function can |
| 1358 | + * The upshot of this behavior is that a SECURITYDEFINER function can |
1359 | 1359 | * create temp tables that can then be accessed (if permission is granted) |
1360 | | - * by code that doesn't have permissions to create temp tables. |
| 1360 | + * by code in the same session that doesn't have permissions to create |
| 1361 | + * temp tables. |
1361 | 1362 | * |
1362 | 1363 | * XXX Would it be safe to ereport a special error message as |
1363 | 1364 | * InitTempTableNamespace does? Returning zero here means we'll get a |
|