| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Row-Level Security Policies (RLS) |
| Date: | 2015-05-22 18:08:07 |
| Message-ID: | 20150522180807.GB5885@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Stephen Frost wrote:
> Row-Level Security Policies (RLS)
What do we need RowSecurityPolicy->policy_id for? It seems to me that
it is only used to determine whether the policy is the "default deny"
one, so that it can later be removed if a hook adds a different one.
This seems contrived as well as under-documented. Why isn't a boolean
flag sufficient?
(Not an actual review of this patch. I was merely skimming the code.)
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-05-22 19:23:32 | Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. |
| Previous Message | Peter Eisentraut | 2015-05-22 16:05:36 | Re: pgsql: At promotion, archive last segment from old timeline with .parti |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-05-22 18:11:42 | Re: RFC: Non-user-resettable SET SESSION AUTHORISATION |
| Previous Message | Josh Berkus | 2015-05-22 18:01:05 | Re: Add a hint when postgresql.conf hot_standby = 'off' and recovery.conf standby = 'on' |