Horton

Re: 8.4 release planning

Peter Eisentraut <peter_e@gmx.net>

View thread View on postgr.es
From: Peter Eisentraut <peter_e@gmx.net>
To: Greg Smith <gsmith@gregsmith.com>
Cc: Chad Sellers <csellers@tresys.com>, Ron Mayer <rm_pg@cheapcomplexdevices.com>, Joshua Brindle <method@manicmethod.com>, Devrim GÜNDÜZ <devrim@gunduz.org>, Tom Lane <tgl@sss.pgh.pa.us>, Stephen Frost <sfrost@snowman.net>, Gregory Stark <stark@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Josh Berkus <josh@agliodbs.com>, "Joshua D. Drake" <jd@commandprompt.com>, Merlin Moncure <mmoncure@gmail.com>, "Jonah H. Harris" <jonah.harris@gmail.com>, Bruce Momjian <bruce@momjian.us>, Bernd Helmle <mailings@oopsware.de>, pgsql-hackers@postgresql.org
Date: 2009-01-28T09:28:02Z
Lists: pgsql-hackers 
Greg Smith wrote:
> PostgreSQL advocacy point, one of the questions Tom asked about a bit 
> upthread is still a bit hazy here.  There are commercial database 
> offerings selling into the "trusted" space already.  While the use-cases 
> you describe make perfect sense, I don't think it's clear to everyone 
> yet if there's a unique draw to a PostgreSQL + selinux solution that the 
> class of customers you're talking about would prefer it to purchasing 
> one of those products.  Is the cost savings the main driver here, or is 
> there something else about a secure LAPP stack that makes it 
> particularly compelling?

According to the data available to me, it is a combination of doing it 
better than the other guys (e.g., a SELinux type interface instead of 
something handcrafted) and the usual cost savings.