Re: Proposed TODO: CREATE .... WITH OWNER;
От | Josh Berkus |
---|---|
Тема | Re: Proposed TODO: CREATE .... WITH OWNER; |
Дата | |
Msg-id | 200410240939.41443.josh@agliodbs.com обсуждение исходный текст |
Ответ на | Re: Proposed TODO: CREATE .... WITH OWNER; (Dennis Bjorklund <db@zigo.dhs.org>) |
Список | pgsql-hackers |
Dennis, > Another observation is that SET SESSION AUTHORIZATION postgres; and RESET > SESSION AUTHORIZATION; would be the same when postgres is the superuser. > By not using the name of the superuser one get the benefit that one can > restore as another superuser (but see the part about acl's below). <snip> > It's also more complicated since in some cases the acl is set to NULL > which means that it has the default priviledges. And the default > privileges always include all privileges for the owner. So if the acl is > NULL then the old owner looses its privileges and the new gets them. Here > we have a different semantics based on an implementation detail that's not > very visible to the user. <snip> Chris K-L came on IRC after you logged off last night. Apparently, he's already fixed all of the above for 8.0. Since I have a "destruction test" available, I'll see how it does. -- Josh Berkus Aglio Database Solutions San Francisco
В списке pgsql-hackers по дате отправления: