Re: [v9.1] sepgsql - userspace access vector cache - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [v9.1] sepgsql - userspace access vector cache
Date
Msg-id CA+TgmoaxQr7vhKGqeFx6=bvJ6-maT2zMEqEEmviwy3C3Zi+pTA@mail.gmail.com
Whole thread Raw
In response to Re: [v9.1] sepgsql - userspace access vector cache  (Kohei Kaigai <Kohei.Kaigai@EMEA.NEC.COM>)
Responses Re: [v9.1] sepgsql - userspace access vector cache
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Kohei Kaigai
Date:
Subject: Re: [v9.1] sepgsql - userspace access vector cache
Next
From: Robert Haas
Date:
Subject: Re: [v9.1] sepgsql - userspace access vector cache