Skip site navigation (1) Skip section navigation (2)

Re: postgres not use table access permissions ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Partyka Robert <bobson(at)saturn(dot)alpha(dot)pl>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: postgres not use table access permissions ?
Date: 2000-11-03 18:22:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Partyka Robert <bobson(at)saturn(dot)alpha(dot)pl> writes:
> #create user bobson with password '1' nocreatedb nocreateuser;
> #create table a (a int4);
> #revoke all on a from public;
> and now from user bobson after conecting to test database:
> #insert into a values ('1');
> INSERT 19104 1

> hmmm... looks like bug. Or I miss something?

Oops.  Strange though, this looks like it must be a very long-standing
bug: aclinsert3 thinks it can delete any zero-permissions item from an
ACL array, whereas aclcheck has a hard-wired assumption that the world
item is always there.  Could we have missed this for this long?

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Partyka RobertDate: 2000-11-03 18:32:55
Subject: Re[2]: postgres not use table access permissions ?
Previous:From: Bruce MomjianDate: 2000-11-03 18:18:23
Subject: Re: Re: [COMMITTERS] pgsql/contrib/pg_dumpaccounts (Makefile README

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group