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

From Caleb Meredith
Subject Can row level security policies also be implemented for views?
Date
Msg-id CABFpK61qMeiVwrFOBU0L=sXqi7X1T_029_a1VbgicxtT_utT3A@mail.gmail.com
Whole thread Raw
Responses Re: Can row level security policies also be implemented for views?  (Stephen Frost <sfrost@snowman.net>)
List pgsql-general
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?

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.

pgsql-general by date:

Previous
From: anj patnaik
Date:
Subject: Re: error messages not getting logged when running script from cron
Next
From: Adrian Klaver
Date:
Subject: Re: error messages not getting logged when running script from cron