Re: [ANN] SE-PostgreSQL 8.2.3-1.0 alpha release

[KaiGai Kohei <kaigai@kaigai.gr.jp>]

>> Run the following script to initialize the database cluster:
>>
>>   # /etc/init.d/sepostgresql initdb
>>
>> The database cluster is generated under /var/lib/sepgsql/data .
> 
> Why do you have a different name and different database location?  Why not 
> just call it postgresql and have the same locations and script names?
> 
> When I make such releases I just use a newer package version.

The same package name or the same database location means that users have
to uninstall the native PostgreSQL. I thought that users can avoid conflict
is better.

>> Run the following script to start up SE-PostgreSQL server, after you
>> confirm the native PostgreSQL server is stopping.
>>
>>   # /etc/init.d/sepostgresql start
> 
> Why must you confirm that the native postgresql server is stopped?  Is it a 
> matter of ports and named pipes for communication with clients?  If you can 
> have both packages installed at the same time then some people will want to 
> run them both at once.

The purpose is to avoid conflict of tcp/5432 port in the most simple way.
If you want to use both package at same time, alternative tcp port should be
written at /etc/sysconfig/sepostgresql .

>> * There is no compatibility between SE-PostgreSQL and PostgreSQL.
>>   You have to pay attention not to destroy your database files
>>   for native PostgreSQL.
> 
> Have you considered enabling "permissive mode" for the database server such 
> that it can run with unlabeled databases?
>
> Why can't "native PostgreSQL" just ignore the labelling?

We have to store a security context of tuple in anywhere, so modifying the file
format was not avoidable. The storage manager of PostgreSQL cannot handle different
file formats, so SE-PostgreSQL cannot run over the unlabeled databased generated
by native PostgreSQL.

It might be possible, but I expect more hooks to the PostgreSQL is necessary.
It will prevent to follow the version-up of native one.

Thanks,

> I think it would be good if all the compatibility options that are available 
> for ext2/3 were available for databases.
-- 
KaiGai Kohei <kaigai@kaigai.gr.jp>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.