Re: [PATCH] SE-PgSQL/tiny rev.2193 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] SE-PgSQL/tiny rev.2193
Date
Msg-id 22827.1248110209@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] SE-PgSQL/tiny rev.2193  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: [PATCH] SE-PgSQL/tiny rev.2193
List pgsql-hackers
Martijn van Oosterhout <kleptog@svana.org> writes:
> I'm asking because from my position it looks like KaiGai is being
> simultaneously told "you patch is too big, make it smaller" and "your
> patch is not complete (with respect to some metric), make it bigger"
> and we need to define a middle ground if we want to avoid the
> appearence of moving goalposts.

Well, the assumption behind the "make it smaller" advice was that
followon patches might re-add (some of) the advanced functionality
once we had a basic connection to SELinux up and running.  So yes,
there's an expectation of the goals changing over time, and I don't
see a reason to apologize for that.

But on the whole the problem is that the community just isn't interested
in this topic.  Every so often somebody pops up and tells us "if you
build it they will come", but there is a complete lack of hard evidence
that there's significant interest out there.  Without that, I don't think
we'll ever get to the point of wanting to put in the work to make it
happen and then support it over time.  This is a huge project, and
taking it seriously will mean draining resources away from other
high-priority issues.  We need way more evidence of interest than has
been presented.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WIP: Deferrable unique constraints
Next
From: Jaime Casanova
Date:
Subject: Re: pg_stat_activity.application_name