From: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | PgHacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [v9.1] sepgsql - userspace access vector cache |
Date: | 2011-06-09 16:39:26 |
Message-ID: | BANLkTi=EQ_AeeE8H28i6OxddOZepygBAdg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2011/6/9 Robert Haas <robertmhaas(at)gmail(dot)com>:
> On Thu, Jun 9, 2011 at 3:59 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)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.
>
> I believe we decided against that previously on the grounds that we
> don't want to add syscaches that might get really really big. In
> particular, there could be a LOT of labelled large objects floating
> around.
>
(Sorry, I missed to Cc: pgsql-hackers, so send again)
As long as we use syscache mechanism to hold security label of
relation or other cached objects, do you think it cause no troubles?
If so, it may be a good idea to distinct cases when we try to reference
the security label of blobs and others.
--
KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-06-09 16:40:08 | Re: tuning autovacuum |
Previous Message | Merlin Moncure | 2011-06-09 16:37:55 | Re: WALInsertLock contention |