Re: Updates of SE-PostgreSQL 8.4devel patches (r1710)
| От | KaiGai Kohei |
|---|---|
| Тема | Re: Updates of SE-PostgreSQL 8.4devel patches (r1710) |
| Дата | |
| Msg-id | 49B7819E.2000101@kaigai.gr.jp обсуждение исходный текст |
| Ответ на | Re: Updates of SE-PostgreSQL 8.4devel patches (r1710) (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
| Ответы |
Re: Updates of SE-PostgreSQL 8.4devel patches (r1710)
|
| Список | pgsql-hackers |
Heikki Linnakangas wrote:
> KaiGai Kohei wrote:
>> * ACL_SELECT_FOR_UPDATE has same value with ACL_UPDATE, so SE-PostgreSQL
>> checks db_table:{update} permission on SELECT ... FOR SHARE OF,
>> instead of db_table:{lock} permission.
>
> This again falls into the category of trying to have more fine-grained
> permissions than vanilla PostgreSQL has. Just give up on the lock
> permission, and let it check update permission instead. Yes, it can be
> annoying that you need update-permission to do SELECT FOR SHARE, but
> that's an existing problem and not in scope for this patch.
Can I consider the term of "problem" means it can be resolved
in the future (v8.5, if possible) version?
--
KaiGai Kohei <kaigai@kaigai.gr.jp>
В списке pgsql-hackers по дате отправления: