Heikki, I updated the SE-PostgreSQL patches: http://sepgsql.googlecode.com/files/sepgsql-core-8.4devel-r1714.patch http://sepgsql.googlecode.com/files/sepgsql-utils-8.4devel-r1714.patch http://sepgsql.googlecode.com/files/sepgsql-policy-8.4devel-r1714.patch http://sepgsql.googlecode.com/files/sepgsql-docs-8.4devel-r1714.patch http://sepgsql.googlecode.com/files/sepgsql-tests-8.4devel-r1714.patch
- List of updates: * Removed the fixupSelectedColsByTrigger() which added ACL_SELECT on requiredPerms, and set a bit of attno=0 on selectedCols. * Removed the invocatin of sepgsqlCheckProcedureExecute() from ExecCallTriggerFunc() These two changes make clear the attitude for trigger functions in SE-PostgreSQL. So, it now considers them as a part of system internal operations. - Scale of patches: * r1714 (the latest revision) 59 files changed, 3622 insertions(+), 10 deletions(-), 4957 modifications(!) * r1710 (previous revision) 60 files changed, 3686 insertions(+), 10 deletions(-), 4952 modifications(!) ... about 70 lines were downsized. Thanks, -- OSS Platform Development Division, NEC KaiGai Kohei <kai...@ak.jp.nec.com> -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
