2010/8/25 KaiGai Kohei <kai...@ak.jp.nec.com>:
>>>>> 7. I think we need to write and include in the fine documentation some
>>>>> "big picture" documentation about enhanced security providers. Of
>>>>> course, we have to decide what we want to say. But the SECURITY LABEL
>>>>> documentation is just kind of hanging out there in space right now; it
>>>>> needs to connect to a broad introduction to the subject.
>>>>>
>>>> OK, I'll try to describe with appropriate granularity.
>>>> Do we need an independent section in addition to the introduction of
>>>> SECURITY LABEL syntax?
>>>
>>> I think so. I suggest a new chapter called "Enhanced Security
>>> Providers" just after "Database Roles and Privileges".
>>>
>> OK,
>>
>
> Now I'm under describing the new chapter.
> http://git.postgresql.org/gitweb?p=users/kaigai/sepgsql.git;a=blob;f=doc/src/sgml/esp.sgml;hb=devel/seclabel
>
> However, I'm wondering whether the topic about security hooks and some
> others are appropriate for the "III. Server Administration" part.
>
> Perhaps, it is a good idea a new section at the last of "Database Roles
> and Privileges" which introduce a fact that PostgreSQL allows plugins
> to make access control decision, and a new chapter in the "VII. Internals"
> part.
>
> How about the idea?

Well, I prefer what I suggested, but of course I'm biased.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to