Re: [GENERAL] column-level update privs + lock table
От | Josh Kupershmidt |
---|---|
Тема | Re: [GENERAL] column-level update privs + lock table |
Дата | |
Msg-id | AANLkTikZRh76EA0xv9Db=fxD+mVCzYBfpHb1YX4nctXm@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [GENERAL] column-level update privs + lock table (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [GENERAL] column-level update privs + lock table
|
Список | pgsql-hackers |
On Mon, Nov 29, 2010 at 10:06 PM, Robert Haas <robertmhaas@gmail.com> wrote: > On Mon, Nov 29, 2010 at 9:37 PM, Josh Kupershmidt <schmiddy@gmail.com> wrote: >> I actually hadn't thought of that, for some reason. >> >> We used to similarly recommend that people handle TRUNCATE privileges >> with a security definer function. That doesn't mean GRANT TRUNCATE >> wasn't a sweet addition to 8.4. > > Hmm, glad you like it (I wrote that). I'm just asking how far we > should go before we decide we catering to use cases that are too > narrow to warrant an extension of the permissions system. I am slightly opposed to adding GRANTs for LOCK TABLE, ANALYZE, VACUUM, etc. The GRANT help page is long enough already, and I doubt many users would use them, even though I might use GRANT LOCK TABLE myself. Josh
В списке pgsql-hackers по дате отправления: