Horton

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

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Kohei Kaigai <Kohei.Kaigai@emea.nec.com>
Cc: Yeb Havinga <yebhavinga@gmail.com>, Kohei KaiGai <kaigai@kaigai.gr.jp>, PgHacker <pgsql-hackers@postgresql.org>
Date: 2011-07-20T16:21:59Z
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 →

  1. Remove the limit on the number of entries allowed in catcaches, and

On Wed, Jul 20, 2011 at 12:04 PM, Kohei Kaigai
<Kohei.Kaigai@emea.nec.com> wrote:
> The sepgsql_restorecon(NULL) assigns default security label on all the
> database objects being controlled, thus, its workload caches security
> label (including text data) of these objects.
> So, ~5MB of difference is an upper limit of syscache usage because of
> SECLABELOID.

No, it's not.  It's just the upper limit of how large it can be on an
*empty* database.  A real database could have hundreds of tables and
views and thousands of columns.  To say nothing of large objects.

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