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

Re: Allow GRANT/REVOKE permissions to be applied to all schema objects with one command

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>,"Matthias Schmidt" <schmidtm(at)mock-software(dot)de>
Subject: Re: Allow GRANT/REVOKE permissions to be applied to all schema objects with one command
Date: 2005-01-31 19:45:39
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3412A75FD@Herge.rcsinc.local (view raw or flat)
Thread:
Lists: pgsql-hackers
> > GRANT SELECT ON ALL TABLES IN public TO phpuser;
> > GRANT SELECT ON NEW TABLES IN public TO phpuser;
> 
> > Really better than this?
> > GRANT { SELECT | INSERT | UPDATE | DELETE | RULE | REFERENCES |
TRIGGER
> > | EXECUTE | CREATE | ALL [ PRIVILEGES ] }    ON SCHEMA schemaname [,
> > ...]
> 
> The latter confuses privileges-for-a-schema with
privileges-for-a-table.

Right.
 
> > This will be faster (FWIW) than a multiple table grant
> > because it's just setting one permission at the schema level.
> I think this argument is bogus, because the savings in time spent to
do

Of course.  GRANT is not really performance sensitive, anyways. Is the
price of looking up a schema a deal breaker here, or is it possible to
avoid it?

Merlin

Responses

pgsql-hackers by date

Next:From: Mitch PirtleDate: 2005-01-31 19:52:08
Subject: Re: Last ID Problem
Previous:From: Tom LaneDate: 2005-01-31 19:40:08
Subject: Re: Group-count estimation statistics

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