| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | calebmeredith8(at)gmail(dot)com |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: BUG #13780: Multiple commands not allowed for creating a policy. |
| Date: | 2015-11-23 12:16:15 |
| Message-ID: | CAB7nPqT986ToW6DpOx=rz-Q_Kbn_HvVcU9us0Vk=R8V3S_6QLQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Nov 22, 2015 at 10:23 PM, <calebmeredith8(at)gmail(dot)com> wrote:
> This doesn't seem to be intended as the GRANT specification allows it, and
> CREATE POLICY supports the ALL command.
>
Yeah, I would tend to agree that the existence of ALL contradicts the
expression constraints that are in place when defining a non-ALL policy as
we could basically ignore either the WITH CHECK or USING clauses defined in
a policy defined depending on the DML or SELECT command used. To be more
exact, for example with an ALL policy that has both a WITH CHECK and USING
defined, we would ignore the USING clause with an INSERT query, right? We
are in beta2 state now, so I don't think anything is going to change, but
Stephen, your thoughts perhaps?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pinker | 2015-11-23 12:27:58 | pg_dump - wrong order with inheritance |
| Previous Message | calebmeredith8 | 2015-11-22 13:23:27 | BUG #13780: Multiple commands not allowed for creating a policy. |