Re: postgres function does not handle PUBLIC - expected? - Mailing list pgsql-admin

From Kevin Grittner
Subject Re: postgres function does not handle PUBLIC - expected?
Date
Msg-id 4C61698D0200002500034469@gw.wicourts.gov
Whole thread Raw
In response to Re: postgres function does not handle PUBLIC - expected?  (Kasia Tuszynska <ktuszynska@esri.com>)
Responses Re: postgres function does not handle PUBLIC - expected?  (Kasia Tuszynska <ktuszynska@esri.com>)
List pgsql-admin
Kasia Tuszynska <ktuszynska@esri.com> wrote:

> We found this issue because we can grant privs to public on a
> table, but could not revoke them.

Odd.

test=# create table t1 (c1 int primary key);
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
"t1_pkey" for table "t1"
CREATE TABLE
test=# grant insert on t1 to public;
GRANT
test=# revoke insert on t1 from public;
REVOKE
test=# revoke update on t1 from public;
REVOKE

> 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:

http://www.postgresql.org/docs/current/static/role-membership.html

As Andre pointed out, you can get a reasonable explanation on the
page describing the GRANT statement.

-Kevin

pgsql-admin by date:

Previous
From: charlie derr
Date:
Subject: Re: postgres function does not handle PUBLIC - expected?
Next
From: charlie derr
Date:
Subject: Re: postgres function does not handle PUBLIC - expected?