| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Bernd Helmle <mailings(at)oopsware(dot)de> |
| Subject: | Re: 8.4 release planning |
| Date: | 2009-01-27 14:36:50 |
| Message-ID: | 20090127143650.GK8123@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter,
* Peter Eisentraut (peter_e(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-01-27 14:39:50 | Re: pg_upgrade project status |
| Previous Message | Heikki Linnakangas | 2009-01-27 14:35:59 | Re: pg_upgrade project status |