| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CREATE POLICY and RETURNING |
| Date: | 2014-10-17 08:24:04 |
| Message-ID: | CAA-aLv5T-LSgOit2e5GNQfTUv4u+sxGupW5_hbPShHFD17qzKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17 October 2014 07:57, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> On 10/17/2014 02:49 AM, Robert Haas wrote:
> > I think you could probably make the DELETE policy control what can get
> > deleted, but then have the SELECT policy further filter what gets
> > returned.
>
> That seems like the worst of both worlds to me.
>
> Suddenly DELETE ... RETURNING might delete more rows than it reports a
> resultset for. As well as being potentially dangerous for people using
> it in wCTEs, etc, to me that's the most astonishing possible outcome of
> all.
>
> I'd be much happier with even:
>
> ERROR: RETURNING not permitted with SELECT row-security policy
>
> than this.
>
+1
This suggestion is most in line with what I would expect to occur.
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicolas Barbier | 2014-10-17 08:47:01 | Re: Materialized views don't show up in information_schema |
| Previous Message | David G Johnston | 2014-10-17 07:16:33 | Re: CREATE POLICY and RETURNING |