Re: Possible typo in create_policy.sgml - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Possible typo in create_policy.sgml
Date
Msg-id CAM3SWZTPn7p9zx8CqCxxr4yXsk1zbwRa+U_M1MGQAVF7AamjCg@mail.gmail.com
Whole thread Raw
In response to Re: Possible typo in create_policy.sgml  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Possible typo in create_policy.sgml
List pgsql-hackers
On Tue, Jan 6, 2015 at 11:25 AM, Stephen Frost <sfrost@snowman.net> wrote:
> Looks reasonable to me.  Amit, does this read better for you?  If so, I
> can handle making the change to the docs.

The docs also prominently say:

"The security-barrier qualifications will always be evaluated prior to
any user-defined functions or user-provided WHERE clauses, while the
with-check expression will be evaluated against the rows which are
going to be added to the table. By adding policies to a table, a user
can limit the rows which a given user can select, insert, update, or
delete. This capability is also known as Row Level Security or RLS."

I would prefer it if it was clearer based on the syntax description
which qual is which. The security barrier qual "expression" should
have an identifier/name in the syntax description that is more
suggestive of "security barrier qual", emphasizing its distinctness
from "check_expression". For example, I think "barrier_expression"
would be clearer.
-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: Updating copyright notices to 2015 for PGDG
Next
From: Simon Riggs
Date:
Subject: Re: parallel mode and parallel contexts