Re: SE-PgSQL developer documentation (Re: Reworks for Access Control facilities (r2363)) - Mailing list pgsql-hackers

From KaiGai Kohei
Subject Re: SE-PgSQL developer documentation (Re: Reworks for Access Control facilities (r2363))
Date
Msg-id 4AE7BE84.60305@ak.jp.nec.com
Whole thread Raw
In response to Re: SE-PgSQL developer documentation (Re: Reworks for Access Control facilities (r2363))  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: SE-PgSQL developer documentation (Re: Reworks for Access Control facilities (r2363))
List pgsql-hackers
Robert Haas wrote:
> 2009/10/27 KaiGai Kohei <kaigai@ak.jp.nec.com>:
>> - no statement support to specify security context.
>>  (It makes impossible to add support in pg_dump. Is it really OK?)
> 
> I doubt that anything without pg_dump support would be even vaguely OK...

In my previous experience, it enabled to reduce 300-400 lines of the patch.
But here is no more sense than the 300-400 lines.

In my honest, I like to include a feature to specify an explicit security
context in the patch from the begining.
(It also allows to attach test cases with more variations.)
-- 
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Where's the docs?
Next
From: Josh Berkus
Date:
Subject: Re: Where's the docs?