| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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 03:40:30 |
| Message-ID: | 20150130034029.GD3854@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> 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.
Excellent, thanks for the feedback. I'll see about making those changes
tomorrow.
Thanks again!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Venkata Balaji N | 2015-01-30 03:48:39 | Re: Redesigning checkpoint_segments |
| Previous Message | Stephen Frost | 2015-01-30 03:37:27 | Re: [COMMITTERS] pgsql: Fix column-privilege leak in error-message paths |