| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Possible typo in create_policy.sgml |
| Date: | 2015-01-30 02:55:22 |
| Message-ID: | CA+TgmobfKw_KDdV3R206RT5fdrUxsapyCa8zeg5n43_=beAQWg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 29, 2015 at 9:04 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> A policy grants the ability to SELECT, INSERT, UPDATE, or DELETE rows
> which match the relevant policy expression. Existing table rows are
> checked against the expression specified via USING, while new rows
> that would be created via INSERT or UPDATE are checked against the
> expression specified via WITH CHECK. When a USING expression returns
> false for a given row, that row is not visible to the user. When a WITH
> CHECK expression returns false for a row which is to be added, an error
> occurs.
Yeah, that's not bad. I think it's an improvement, in fact.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-01-30 02:59:02 | Re: jsonb, unicode escapes and escaped backslashes |
| Previous Message | Michael Paquier | 2015-01-30 02:54:51 | Re: pg_check_dir comments and implementation mismatch |