Updates of SE-PostgreSQL 8.4devel patches (r1668) - Mailing list pgsql-hackers

From KaiGai Kohei
Subject Updates of SE-PostgreSQL 8.4devel patches (r1668)
Date
Msg-id 49ACDEB2.2090600@ak.jp.nec.com
Whole thread Raw
In response to Updates of SE-PostgreSQL 8.4devel patches (r1627)  (KaiGai Kohei <kaigai@ak.jp.nec.com>)
Responses Re: Updates of SE-PostgreSQL 8.4devel patches (r1668)  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
The series of SE-PostgreSQL patches for v8.4 were updated:

[1/5] http://sepgsql.googlecode.com/files/sepgsql-core-8.4devel-r1668.patch
[2/5] http://sepgsql.googlecode.com/files/sepgsql-utils-8.4devel-r1668.patch
[3/5] http://sepgsql.googlecode.com/files/sepgsql-policy-8.4devel-r1668.patch
[4/5] http://sepgsql.googlecode.com/files/sepgsql-docs-8.4devel-r1668.patch
[5/5] http://sepgsql.googlecode.com/files/sepgsql-tests-8.4devel-r1668.patch

- List of updates: * It is rebased to the latest CVS HEAD. * sepgsqlCheckProcedureInstall() is moved to sepgsql/hooks.c
from  sepgsql/perms.c, like as other sepgsqlCheckXXXX() is delopyed on. * sepgsqlCheckDatabaseAccess() is moved to
pg_database_aclcheck()  from pg_database_aclmask(), because pg_aclmask() can be invoked   on ExecGrant_xxxx, but
SE-PostgreSQLshould not intervene existing   DAC policy. * sepgsqlCheckProcedureExecute() is moved to
pg_proc_aclcheck()  in same reason.
 

These changes are obvious and minor, and rest of implementations
keep unchanged, so don't consider this updates needs to review
whole of patches again, please.

I would like to know the current status of reviewing the patches.
It is welcome, if it is not still 100% completed and partial ones.
And, please tell me, if I missed anything.
Anyway, it is obvious we don't have enough time!

Thanks,
-- 
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>


pgsql-hackers by date:

Previous
From: ITAGAKI Takahiro
Date:
Subject: Why do we keep UnusedLock1 in LWLockId?
Next
From: Heikki Linnakangas
Date:
Subject: Re: Why do we keep UnusedLock1 in LWLockId?