| 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-26 14:44:06 |
| Message-ID: | 20150526144406.GU5885@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Stephen Frost wrote:
> Alvaro,
>
> * Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> > 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?
>
> Thanks for taking a look!
>
> It's also used during relcache updates (see equalPolicy()).
Hmm, but the policy name is unique also, right? So the policy_id check
is redundant ...
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2015-05-26 15:24:00 | pgsql: Add all structured objects passed to pushJsonbValue piecewise. |
| Previous Message | Stephen Frost | 2015-05-26 13:08:00 | Re: [COMMITTERS] pgsql: Row-Level Security Policies (RLS) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-05-26 15:01:59 | Re: ERROR: MultiXactId xxxx has not been created yet -- apparent wraparound |
| Previous Message | Tom Lane | 2015-05-26 14:41:12 | Re: fsync-pgdata-on-recovery tries to write to more files than previously |