Horton

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

Yeb Havinga <yebhavinga@gmail.com>

View thread
From: Yeb Havinga <yebhavinga@gmail.com>
To: Kohei Kaigai <Kohei.Kaigai@emea.nec.com>
Cc: PgHacker <pgsql-hackers@postgresql.org>
Date: 2011-07-21T19:32:54Z
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

> Is it possible to only include the syscache on --enable-selinux 
> configurations? It would imply physical data incompatibility with 
> standard configurations, but that's also true for e.g. the block size.
>
> Also, the tests I did with varying bucket sizes suggested that 
> decreasing the syscache to 256 didn't show a significant performance 
> decrease compared to the 2048 #buckets, for the restorecon test, which 
> hits over 3000 objects with security labels. My guess is that that is 
> a fair middle of the road database schema size. Are you unwilling to 
> pay the startup overhead for a extra 256 syscache?
>

Hello KaiGai-san,

off-list,

I was wondering why the catalog pg_seclabel exists at all. Why not store 
the labels together with the objects (pg_class, pg_attribute etc) ? The 
syscache wouldn't be needed in that case.

regards,
Yeb