Peter, Abhijit,
Could you tell me the current status of reviewing process in the CommitFest:Sep?
I can understand the patches contain several new concept and a bit large,
and it is a tough work to review them comprehensively.
I'm not unconcern anything even if reviwing comments are partial one.
However, I cannot improve anything without any comments. :(
Did the previous message which I posted help you to understand the patches?
If not, please feel free to ask me anything.
Thanks,
KaiGai Kohei wrote:
Hello,
The latest SE-PostgreSQL patches are updated here:
[1/4]
http://sepgsql.googlecode.com/files/sepostgresql-sepgsql-8.4devel-3-r1005.patch
[2/4] http://sepgsql.googlecode.com/files/sepostgresql-pg_dump-8.4devel-3-r1005.patch
[3/4] http://sepgsql.googlecode.com/files/sepostgresql-policy-8.4devel-3-r1005.patch
[4/4] http://sepgsql.googlecode.com/files/sepostgresql-docs-8.4devel-3-r1005.patch
They contains rebasing to the CVS HEAD, because we cannot apply the
previous ones
correctly due to progress in the base version.
Rest of changes are here:
- A new PGACE hook: pgaceIsAllowExecutorRunHook().
It enables to control overriding ExecutorRun_hook, because several
important
hooks are invoked from standard_ExecutorRun().
- T_SEvalItem related equalXXXX() functions are added to
nodes/equalfuncs.c.
# I've left for implement them.
- Fix typo in src/include/security/pgace.h
BTW, I thought I have to show the overview of the patch to help reviwers.
The main patch ([1/4]) is especially big and contains new concepts.
The following explanation shows several key concept of SE-PostgreSQL.
I'm happy if it can reduce the load of reviwers.
No need to say, please feel free to ask me anything. :-)
Thanks,
--
OSS Platform Development Division, NEC
KaiGai Kohei <[EMAIL PROTECTED]>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
