Re: security label support, revised

The attached patch can be applied on the Robert's seclabel-v4.patch.

It contains the following stuffs.
* The "dummy_esp" module and regression test for SECURITY LABEL statement.
   This module allows only four labels: "unclassified", "classified",
   "secret" and "top secret". The later two labels can be set by only
   superusers. The new regression test uses this "dummy_esp" module to
   find out future regression in SECURITY LABEL statement.
* A minimum description about external security provider at the tail
   of Database Roles and Privileges  chapter.
* Add pg_seclabels system view
* Revising pg_dump/pg_dumpall
   - '--security-label' was replaced by '--no-security-label'
   - implemented according to the manner in comments.
     findSecLabels() and collectSecLabels() are added to reduce number of
     SQL queries, in addition to dumpSecLabel().

Thanks,

(2010/09/24 21:58), Robert Haas wrote:
> On Fri, Sep 24, 2010 at 8:54 AM, KaiGai Kohei<kaigai@kaigai.gr.jp>  wrote:
>> (2010/09/24 20:56), Robert Haas wrote:
>>>
>>> 2010/9/23 KaiGai Kohei<kaigai@ak.jp.nec.com>:
>>>>>
>>>>> Please see
>>>>> http://archives.postgresql.org/pgsql-hackers/2010-09/msg01080.php
>>>>>
>>>> OK, I'll emulate this approach at first.
>>>
>>> Don't worry about this part - I will do this myself.  If you can just
>>> fix the pg_dump stuff, I think we will be in pretty good shape.
>>>
>> Ahh, I already did this part at the today's afternoon:
>>   http://bit.ly/9kOsnx
>>
>> And, the pg_dump stuff has been just implemented(, but not tested yet):
>>   http://bit.ly/a0eVfL
>>   If you prefer to keep the patch small, I'll revert the system_views.sql
>> in the next patch.
>
> It probably doesn't matter much - it'll likely take me about the same
> amount of time to check your work as it would to do it myself, so it's
> pretty much six of one, half a dozen of the other.
>


--
KaiGai Kohei <kaigai@kaigai.gr.jp>