The SE-PostgreSQL patches (for v8.5) are updated: http://sepgsql.googlecode.com/files/sepgsql-01-sysatt-8.4beta1-r1891.patch http://sepgsql.googlecode.com/files/sepgsql-02-core-8.4beta1-r1891.patch http://sepgsql.googlecode.com/files/sepgsql-03-writable-8.4beta1-r1891.patch http://sepgsql.googlecode.com/files/sepgsql-04-rowlevel-8.4beta1-r1891.patch http://sepgsql.googlecode.com/files/sepgsql-05-perms-8.4beta1-r1891.patch http://sepgsql.googlecode.com/files/sepgsql-06-utils-8.4beta1-r1891.patch http://sepgsql.googlecode.com/files/sepgsql-07-tests-8.4beta1-r1891.patch http://sepgsql.googlecode.com/files/sepgsql-08-docs-8.4beta1-r1891.patch List of updates: * The base version was upgraded to the latest CVS HEAD. * db_schema, db_sequence object classes were added. These classes provide analogy of ACL_USAGE and so on. * db_table/db_column:{reference} permission was added. * Some of bug were fixed. BTW, Bruce, > > In the v8.4, it seems to me more appropriate that the "Appendix G. External > > > Projects" points to a few external (but not mainlined yet) projects such as > > > SE-PostgreSQL. > > Ah, very good idea. I made a wiki entry at: http://wiki.postgresql.org/wiki/SEPostgreSQLv8.4 It notes the step to apply the SE-PostgreSQL patches to v8.4 series, and will introduce the list of patches for each v8.4 series. (I'll start to provide them from v8.4beta2.) Is it similar to what you imagined? If OK, I'll send a documentation patch for the appendix. Thanks, -- OSS Platform Development Division, NEC KaiGai Kohei <kaigai@ak.jp.nec.com>
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных