| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Gregory Smith <gregsmithpgsql(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, jeff(dot)mccormick(at)crunchydatasolutions(dot)com |
| Subject: | Re: row security roadmap proposal |
| Date: | 2013-12-17 17:03:27 |
| Message-ID: | CA+TgmoY+JDWK6_u-vUV5PX43jYDxrRRUkVqxHYvR_svLHc44nw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 16, 2013 at 3:12 PM, Gregory Smith <gregsmithpgsql(at)gmail(dot)com> wrote:
> On 12/16/13 9:36 AM, Craig Ringer wrote:
>>
>> - Finish and commit updatable security barrier views. I've still got a
>> lot of straightening out to do there.
>
> I don't follow why you've put this part first. It has a lot of new
> development and the risks that go along with that, but the POC projects I've
> been testing are more interested in the view side issues.
I don't really see a way that any of this can work without that. To
be clear, that work is required even just for read-side security.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-12-17 17:07:38 | Re: patch: make_timestamp function |
| Previous Message | Pavel Stehule | 2013-12-17 16:56:22 | Re: patch: make_timestamp function |