Horton

Re: 8.4 release planning

Stephen Frost <sfrost@snowman.net>

View thread View on postgr.es
From: Stephen Frost <sfrost@snowman.net>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>, Josh Berkus <josh@agliodbs.com>, "Joshua D. Drake" <jd@commandprompt.com>, Robert Haas <robertmhaas@gmail.com>, Merlin Moncure <mmoncure@gmail.com>, "Jonah H. Harris" <jonah.harris@gmail.com>, Gregory Stark <stark@enterprisedb.com>, Simon Riggs <simon@2ndquadrant.com>, Bruce Momjian <bruce@momjian.us>, Bernd Helmle <mailings@oopsware.de>
Date: 2009-01-27T14:36:50Z
Lists: pgsql-hackers 
Peter,

* Peter Eisentraut (peter_e@gmx.net) wrote:
> As one of the earlier reviewers, I think the design is OK, but the way the 
> implementation is presented was not acceptable, and very little has been 
> accomplished in terms of reacting to our comments.  For example, where is the 
> SQL row security feature, which should have been designed, implemented, and 
> committed separately, in the opinion of most commentaries.

Eh?  Are you thinking of column-level privileges, which was committed
last week?  The SQL spec doesn't define row-level security, and coming
up with something willy-nilly on our own doesn't really strike me as the
best approach.  Oracle, SQL Server, etc, also use the security labels
concept that the SE-PostgreSQL patch implements.

	Thanks,

		Stephen