Permissions problem

From: Chris Dunlop <chris(at)onthe(dot)net(dot)au>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Permissions problem
Date: 2001-05-03 01:54:26
Message-ID: 20010503115426.A4937@minotaur.onthe.net.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

There seems to be a minor bug related to permissions. If you create a
table and grant permissions on that table to someone else, you lose your
own permissions (note: do this as a non-dbadmin account):

testdb=> create table tester ( test int4 );
CREATE
testdb=> insert into tester values ('1');
INSERT 17109139 1
testdb=> grant select on tester to someone;
CHANGE
testdb=> insert into tester values ('2');
ERROR: tester: Permission denied.
testdb=>

>From postgres/sql-grant.htm:

Description

GRANT allows the creator of an object to give specific permissions to
all users (PUBLIC) or to a certain user or group. Users other than
the creator don't have any access permission unless the creator
GRANTs permissions, after the object is created.

Once a user has a privilege on an object, he is enabled to exercise
that privilege. There is no need to GRANT privileges to the creator
of an object, the creator automatically holds ALL privileges, and can
also drop the object.

It's not behaving as documented ("There is no need to GRANT privileges
to the creator of an object").

This is in postgresql-7.0.3, but it's possible this is fixed in a more
recent version - can someone try this and see what happens ?

Cheers,

Chris.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-05-03 03:46:11 Re: Permissions problem
Previous Message Bruce Momjian 2001-05-03 01:48:25 Re: Collation order for btree-indexable datatypes