| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Caleb Meredith <calebmeredith8(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Can row level security policies also be implemented for views? |
| Date: | 2015-12-02 22:46:11 |
| Message-ID: | 565F74B3.6040008@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/25/15 7:40 AM, Stephen Frost wrote:
>> It seems easy conceptually, RLS just adds a WHERE clause to queries if I'm
>> >not mistaken, and conceptually a view is just a query. The CURRENT_USER
>> >issue is valid, but personally it's not too big for me as most auth is done
>> >through database parameters.
> The hard part is making sure that what happens when there are policies
> on views actually makes sense and works as users expect.
Could this potentially be worked around by having a view that pulls from
an SRF? Possibly an SRF that's using a dynamically constructed query?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Caleb Meredith | 2015-12-02 22:59:30 | Re: Can row level security policies also be implemented for views? |
| Previous Message | Jim Nasby | 2015-12-02 22:43:53 | Re: full_page_writes on SSD? |