| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, pgsql-hackers(at)postgresql(dot)org, heikki(dot)linnakangas(at)enterprisedb(dot)com |
| Subject: | Re: [RFC] A tackle to the leaky VIEWs for RLS |
| Date: | 2010-06-01 16:39:20 |
| Message-ID: | 20100601163920.GV21875@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Greg Stark (gsstark(at)mit(dot)edu) wrote:
> Also incidentally I'm having trouble imagining a scenario where this
> really matters. For it to be an issue you would have to simultaneously
> have a user which can't access all the data and must go through views
> which limit the data he can access -- and has privileges to issue DDL
> to create functions and operators. That seems like an unlikely
> combination. I've seen views used before to restrict the role accounts
> used by front-end applications but those accounts have no DDL
> privileges.
Erm, I have to disagree with this in general.. We don't all just build
web apps. On multi-user databases, this really isn't that uncommon.
I'm not saying it's an everyday kind of thing, but I don't think this
issue is something we can just ignore either.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-06-01 16:52:42 | Re: [RFC] A tackle to the leaky VIEWs for RLS |
| Previous Message | Jan Wieck | 2010-06-01 16:27:34 | Re: exporting raw parser |