Re: [v9.1] sepgsql - userspace access vector cache
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Kohei KaiGai <kaigai@kaigai.gr.jp>
Cc: PgHacker <pgsql-hackers@postgresql.org>
Date: 2011-06-09T16:37:22Z
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
* Kohei KaiGai (kaigai@kaigai.gr.jp) wrote: > The only modification by this patch to the core routine is a new > syscache for pg_seclabel system catalog. The SECLABELOID enables to > reference security label of the object using syscache interface. Perhaps I'm missing it, but.. why is this necessary to implement such a cache? Also, I thought the SELinux userspace libraries provided a cache solution? This issue is hardly unique to SELinux in PostgreSQL... THanks, Stephen