| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ON CONFLICT issues around whole row vars, |
| Date: | 2015-10-05 12:17:18 |
| Message-ID: | CAOuzzgoZCtyOFhZbQWZsssiHprue=D1ovoQgKbLNVbqhcTmt2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres,
On Monday, October 5, 2015, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2015-10-05 08:01:00 -0400, Stephen Frost wrote:
> > Peter, all,
> > I had intended to address with policies what is addressed through
> > permissions with 7d8db3e, but the coverage for INSERT+RETURNING was only
> > done when ON CONFLICT was in use.
> >
> > I've fixed that by applying the SELECT policies as WCOs for both the
> > INSERT and UPDATE RETURNING cases. This matches the permissions system,
> > where we require SELECT rights on the table for an INSERT RETURNING
> > query.
>
> This really needs tests verifying the behaviour...
>
Good point, will add.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2015-10-05 12:20:38 | Re: Parallel Seq Scan |
| Previous Message | Andres Freund | 2015-10-05 12:14:19 | Re: ON CONFLICT issues around whole row vars, |