| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Sounak Chakraborty <sounakr(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Row level security implementation in Foreign Table in Postgres |
| Date: | 2016-11-03 15:18:30 |
| Message-ID: | CA+TgmoaJ3mOXyphmWUAoBs7EJHAF5c-Qfn52GK2q8xKTJHQbNw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 2, 2016 at 10:46 PM, Sounak Chakraborty <sounakr(at)gmail(dot)com> wrote:
> Row level security feature implementation in Postgres is through policy and the row security qualifier is attached as a subquery 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 of enabling 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 passed for 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2016-11-03 15:28:33 | Re: pageinspect: Hash index support |
| Previous Message | Robert Haas | 2016-11-03 15:15:24 | Re: Patch to implement pg_current_logfile() function |