| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Charles Clavadetscher <clavadetscher(at)swisspug(dot)org> |
| Subject: | Re: unclear about row-level security USING vs. CHECK |
| Date: | 2015-09-28 19:42:59 |
| Message-ID: | CA+TgmoaGP1xgz-Lq7EORSRxQXZufdykLrZj1ppPs3OPSsHA2PA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 28, 2015 at 3:15 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> I listed out the various alternatives but didn't end up getting any
> responses to it. I'm still of the opinion that the documentation is the
> main thing which needs improving here, but we can also change CREATE
> POLICY, et al, to require an explicit WITH CHECK clause for the commands
> where that makes sense if that's the consensus.
My vote is to remove the behavior where USING flows over to WITH
CHECK. So you only get a WITH CHECK policy if you explicitly specify
one.
If there's some other consensus, OK, but tempus fugit.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-09-28 19:50:49 | Re: row_security GUC, BYPASSRLS |
| Previous Message | Stephen Frost | 2015-09-28 19:42:40 | Re: Rename withCheckOptions to insertedCheckClauses |