Re: [v9.1] sepgsql - userspace access vector cache

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Kohei Kaigai <Kohei.Kaigai@emea.nec.com>

Cc: Kohei KaiGai <kaigai@kaigai.gr.jp>, PgHacker <pgsql-hackers@postgresql.org>, Yeb Havinga <yebhavinga@gmail.com>

Date: 2011-09-27T12:38:36Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Remove the limit on the number of entries allowed in catcaches, and
- 8b9bc234ad43 8.2.0 cited

On Fri, Sep 2, 2011 at 12:38 PM, Kohei Kaigai <Kohei.Kaigai@emea.nec.com> wrote:
>> I've committed this, but I still think it would be helpful to revise
>> that comment.  The turn "boosted up" is not very precise or
>> informative.  Could you submit a separate, comment-only patch to
>> improve this?
>>
> I tried to put more detailed explanation about the logic of do { ... } while
> loop of sepgsql_avc_check_valid and the cache field of new security label to
> be switched on execution of the procedure. Is it helpful?

I edited this and committed it along with a bunch of further
wordsmithing on the comments in that file.  Please let me know if you
see any isuses.

Thanks,

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