rpms/sepostgresql/devel postgresql-8.2.6.tar.gz, NONE, 1.1 .cvsignore, 1.4, 1.5 sepostgresql.init, 1.8, 1.9 sepostgresql.spec, 1.8, 1.9 sepostgresql.te, 1.8, 1.9
Kohei KaiGai
kaigai at ak.jp.nec.com
Wed Jan 16 03:39:42 UTC 2008
- Previous message: rpms/sepostgresql/devel postgresql-8.2.6.tar.gz, NONE, 1.1 .cvsignore, 1.4, 1.5 sepostgresql.init, 1.8, 1.9 sepostgresql.spec, 1.8, 1.9 sepostgresql.te, 1.8, 1.9
- Next message: autoconf issue using -stdc=gnu++0x option in AC_CHECK_HEADER macro.
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Tom Lane wrote:
> BTW, I'm planning to push postgresql 8.3 into rawhide very soon (actually
> it'll likely be 8.3RC2 at first, just to make sure it gets in there
> before F9 alpha freeze). Don't know what impact that will have on
> sepostgresql. If you won't be ready to update, it might be necessary
> to decouple the two packages after all.
>
> regards, tom lane
I've ported sepostgresql features into 8.3 based postgresql for a while.
See, http://sepgsql.googlecode.com/svn/ .
"/trunk" is already designed for 8.3RC1 based sepostgresql.
There will be an impact indeed, but it's not a negative one.
On the 8.3 based sepostgresql, it stores security attribute of HeapTuple
using the t_hoff padding area as you suggested at:
https://bugzilla.redhat.com/show_bug.cgi?id=249522#c58
This is a reson why we cannot share any *.so libraries, as is.
However, I believe this change enables to share most of contrib packages
without any changing/rebuilding.
Thanks,
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai at ak.jp.nec.com>
- Previous message: rpms/sepostgresql/devel postgresql-8.2.6.tar.gz, NONE, 1.1 .cvsignore, 1.4, 1.5 sepostgresql.init, 1.8, 1.9 sepostgresql.spec, 1.8, 1.9 sepostgresql.te, 1.8, 1.9
- Next message: autoconf issue using -stdc=gnu++0x option in AC_CHECK_HEADER macro.
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the devel
mailing list