| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Caleb Meredith <calebmeredith8(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Can row level security policies also be implemented for views? |
| Date: | 2015-12-03 23:53:53 |
| Message-ID: | 5660D611.403@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/3/15 7:17 AM, Caleb Meredith wrote:
> Yes it probably could be solved by this. Just a trigger which replaces
> SELECT right?
It's not a trigger and I don't know what you mean by replacing select.
An SRF can return anything you want it to.
My suggestion was to run a standard select statement (possibly a dynamic
one via EXECUTE) from the SRF, in the hope that the system would just
consider that to be a plain-old SELECT against the table, allowing RLS
to function.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Selim Tuvi | 2015-12-04 00:03:31 | BDR: ALTER statement hanging |
| Previous Message | Jim Nasby | 2015-12-03 23:47:40 | Re: Pgbasebackup help |