Re: Updates of SE-PostgreSQL 8.4devel patches (r1268) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Updates of SE-PostgreSQL 8.4devel patches (r1268)
Date
Msg-id 493FB920.6020308@gmx.net
Whole thread Raw
In response to Re: Updates of SE-PostgreSQL 8.4devel patches (r1268)  (KaiGai Kohei <kaigai@kaigai.gr.jp>)
Responses Re: Updates of SE-PostgreSQL 8.4devel patches (r1268)
List pgsql-hackers
KaiGai Kohei wrote:
> I don't agree. What is the reason why? It has been unclear for me.
> 
> The PGACE security framework is designed to allow users to choose
> an enhanced security mechanism from some of provided options.
> (Currently, we have sepgsql and rowacl.)
> It is quite natural that one is disabled when the other is enabled.

As a general rule, mutually exclusive features as compile-time option 
should be avoided at all costs.  Since most people use binary packages, 
forcing the packager to make such a choice will always make a lot of 
people unhappy, or alternatively cause one of the features to bitrot.

As a secondary rule, mutually exclusive features should be avoided at 
all, without a compelling reason.  I don't see such a reason here.


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Sync Rep: First Thoughts on Code
Next
From: "Robert Haas"
Date:
Subject: Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine