Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
0f3f34f0
Commit
0f3f34f0
authored
21 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Fix minor error in comment.
parent
d7074954
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/backend/catalog/aclchk.c
+4
-3
4 additions, 3 deletions
src/backend/catalog/aclchk.c
with
4 additions
and
3 deletions
src/backend/catalog/aclchk.c
+
4
−
3
View file @
0f3f34f0
...
@@ -8,7 +8,7 @@
...
@@ -8,7 +8,7 @@
*
*
*
*
* IDENTIFICATION
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/catalog/aclchk.c,v 1.10
1
2004/05/28 16:
1
7:1
4
tgl Exp $
* $PostgreSQL: pgsql/src/backend/catalog/aclchk.c,v 1.10
2
2004/05/28 16:
3
7:1
1
tgl Exp $
*
*
* NOTES
* NOTES
* See acl.h.
* See acl.h.
...
@@ -1355,9 +1355,10 @@ pg_namespace_aclmask(Oid nsp_oid, AclId userid,
...
@@ -1355,9 +1355,10 @@ pg_namespace_aclmask(Oid nsp_oid, AclId userid,
*
*
* This may seem redundant given the check in InitTempTableNamespace,
* This may seem redundant given the check in InitTempTableNamespace,
* but it really isn't since current user ID may have changed since then.
* but it really isn't since current user ID may have changed since then.
* The upshot of this behavior is that a SECURITY
INVOK
ER function can
* The upshot of this behavior is that a SECURITY
DEFIN
ER function can
* create temp tables that can then be accessed (if permission is granted)
* 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
* XXX Would it be safe to ereport a special error message as
* InitTempTableNamespace does? Returning zero here means we'll get a
* InitTempTableNamespace does? Returning zero here means we'll get a
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment