Re: Row level security implementation in Foreign Table in Postgres - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Row level security implementation in Foreign Table in Postgres
Date
Msg-id CA+TgmoaJ3mOXyphmWUAoBs7EJHAF5c-Qfn52GK2q8xKTJHQbNw@mail.gmail.com
Whole thread Raw
In response to Row level security implementation in Foreign Table in Postgres  (Sounak Chakraborty <sounakr@gmail.com>)
Responses Re: Row level security implementation in Foreign Table in Postgres  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Nov 2, 2016 at 10:46 PM, Sounak Chakraborty <sounakr@gmail.com> wrote:
> Row level security feature implementation in Postgres is through policy and the row security qualifier is attached as
asubquery to the main query before query planning. The RLS is implemented through ALTER TABLE STATEMENT.
 
> But my doubt is why this feature is not enabled in case of Foreign Table. (ALTER FOREIGN TABLE doesn't have a option
ofenabling Row Level Security).
 
> Is this is not implemented due to some limitations in the current design?
> Because from a quick view it looks like the security subquery can also be easily attached to the main query and
passedfor processing in foreign database.
 

Yeah, I don't see why that couldn't be made to work.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Patch to implement pg_current_logfile() function
Next
From: Peter Eisentraut
Date:
Subject: Re: pageinspect: Hash index support