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

From Stephen Frost
Subject Re: Can row level security policies also be implemented for views?
Date
Msg-id 20151125134025.GV3685@tamriel.snowman.net
Whole thread Raw
In response to Can row level security policies also be implemented for views?  (Caleb Meredith <calebmeredith8@gmail.com>)
Responses Re: Can row level security policies also be implemented for views?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-general
Caleb,

* Caleb Meredith (calebmeredith8@gmail.com) wrote:
> I'm developing an application where strict control of my data is important.
> Views allow me to build a strict custom reading experience, allowing me to
> add computed columns and hide private and metadata columns. Row level
> security allows me strict write control of my data. However, I can't use
> both technologies together, why?

The short and simple answer is that it simply hasn't been done yet.

> 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.

Thanks!

Stephen

Attachment

pgsql-general by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: Query failed: ERROR: character with byte sequence 0xc2 0x96 in encoding "UTF8" has no equivalent in encoding "WIN1250"
Next
From: Stephen Frost
Date:
Subject: Re: "trust" authentication in pg_hba.conf