| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adam Brightwell <adam(dot)brightwell(at)crunchydatasolutions(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Yeb Havinga <yeb(dot)havinga(at)portavita(dot)nl> |
| Subject: | Re: RLS Design |
| Date: | 2014-07-09 06:07:17 |
| Message-ID: | 20140709060717.GG16422@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
KaiGai,
* Kohei KaiGai (kaigai(at)kaigai(dot)gr(dot)jp) wrote:
> What I'd like to implement is adjustment of query like:
> SELECT * FROM t1 WHERE (x like '%abc%') AND (quals by built-in RLS)
> AND (quals by extension-1) AND ... AND (quals by extension-N);
> I never mind even if qualifiers in the second block are connected with OR'd
> manner, however, I want RLS infrastructure to accept additional security
> models provided by extensions.
Would having a table-level 'AND'-vs-'OR' modifier for the RLS policies
on that table be sufficient for what you're looking for? That seems a
simple enough addition which would still allow more complex groups to be
developed later on...
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-07-09 06:10:37 | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
| Previous Message | Stephen Frost | 2014-07-09 06:04:02 | Re: RLS Design |