Partyka Robert <bobson(at)saturn(dot)alpha(dot)pl> writes:
> #create user bobson with password '1' nocreatedb nocreateuser;
> CREATE
> #create table a (a int4);
> CREATE
> #revoke all on a from public;
> CHANGE
> 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

• postgres not use table access permissions ? at 2000-11-03 17:57:43 from Partyka Robert

Responses

• Re[2]: postgres not use table access permissions ? at 2000-11-03 18:32:55 from Partyka Robert
• Re: postgres not use table access permissions ? at 2000-11-03 20:19:52 from Tom Lane

pgsql-hackers by date

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