Re: [COMMITTERS] pgsql: Row-Level Security Policies (RLS) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [COMMITTERS] pgsql: Row-Level Security Policies (RLS)
Date
Msg-id 20150526144406.GU5885@postgresql.org
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Row-Level Security Policies (RLS)  (Stephen Frost <sfrost@snowman.net>)
Responses Re: [COMMITTERS] pgsql: Row-Level Security Policies (RLS)  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost wrote:
> Alvaro,
> 
> * Alvaro Herrera (alvherre@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: fsync-pgdata-on-recovery tries to write to more files than previously
Next
From: Alvaro Herrera
Date:
Subject: Re: "unaddressable bytes" in BRIN