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:
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.
OSS Platform Development Division, NEC
KaiGai Kohei <firstname.lastname@example.org>
fedora-devel-list mailing list