Re: Can row level security policies also be implemented for views? - Mailing list pgsql-general

From Caleb Meredith
Subject Re: Can row level security policies also be implemented for views?
Date
Msg-id CABFpK63wXqXeWO=o16WuRu0YARva=x=WY_b-yUXtBWdNydpE0g@mail.gmail.com
Whole thread Raw
In response to Re: Can row level security policies also be implemented for views?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-general
What is an SRF?

On Wed, Dec 2, 2015 at 5:46 PM Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: plperlu stored procedure seems to freeze for a minute
Next
From: Kaare Rasmussen
Date:
Subject: Re: json indexing and data types