Re: Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped)
От | Alvaro Herrera |
---|---|
Тема | Re: Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped) |
Дата | |
Msg-id | 20070511202749.GA3234@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped) (Russell Smith <mr-russ@pws.com.au>) |
Ответы |
Re: Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped)
|
Список | pgsql-bugs |
So the discussion died again with nothing being decided. I see we have several choices: 1. implement the standard, per Russell suggestion below 2. decide that the standard is braindead and just omit dumping the grantor when it's no longer available, but don't remove pg_auth_members.grantor 3. decide that the standard is braindead and remove pg_auth_members.grantor Which do people feel should be implemented? I can do whatever we decide; if no one has a strong opinion on the matter, my opinion is we do (2) which is the easiest. Russell Smith wrote: > My possible suggestion is; > 1. Implement the standard for revoking only your privileges by default. > 2. Allow the object owner to revoke privileges assigned by any role, as > if you drop and recreate the object you can achieve this anyway. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
В списке pgsql-bugs по дате отправления: