Per my original email, we were calling the has_table_privilege function to revoke rather than simply revoking.
Thank you very much,
From: Kevin Grittner [mailto:Kevin(dot)Grittner(at)wicourts(dot)gov]
Sent: Tuesday, August 10, 2010 1:00 PM
To: Kasia Tuszynska; Szymon Guz
Subject: RE: [ADMIN] postgres function does not handle PUBLIC - expected?
Kasia Tuszynska <ktuszynska(at)esri(dot)com> wrote:
> We found this issue because we can grant privs to public on a
> table, but could not revoke them.
test=# create table t1 (c1 int primary key);
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"t1_pkey" for table "t1"
test=# grant insert on t1 to public;
test=# revoke insert on t1 from public;
test=# revoke update on t1 from public;
> If I did not "know" that public was there how
> would I check for it's existence on Postgres?
You would need to go to the documentation. Unfortunately, we don't
mention it on this page:
As Andre pointed out, you can get a reasonable explanation on the
page describing the GRANT statement.
In response to
pgsql-admin by date
|Next:||From: Greg Smith||Date: 2010-08-11 00:51:11|
|Subject: Re: The function of lock file named ".s.PGSQL.<port>.lock"
|Previous:||From: charlie derr||Date: 2010-08-10 20:00:42|
|Subject: Re: postgres function does not handle PUBLIC - expected?|