| 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 20:47:40 |
| Message-ID: | 20090127204740.GR8123@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Peter Eisentraut (peter_e(at)gmx(dot)net) wrote:
> > 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.
>
> Exactly. But there is plenty of discussion on that elsewhere.
That's the nice thing about the SE-PostgreSQL patch.. It's at least
following established row-level security setups in other enterprise
RDBMSs... The folks coming out now and saying we should require using a
WHERE clause or similar would cause a serious deviation from what's
being done today, without any real change or advantage that I see..
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2009-01-27 20:51:31 | Re: 8.4 release planning |
| Previous Message | Tom Lane | 2009-01-27 20:46:22 | Re: 8.4 release planning |