| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: INSERT ... ON CONFLICT UPDATE and RLS |
| Date: | 2015-01-09 00:49:24 |
| Message-ID: | 20150109004924.GK3062@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter,
* Peter Geoghegan (pg(at)heroku(dot)com) wrote:
> For column level privileges, you wouldn't expect to only get an error
> about not having the relevant update permissions at runtime, when the
> update path happens to be taken. And so it is for RLS.
Right, that's the precedent we should be considering. Column-level
privileges is a great example- you need both insert and update
privileges for the columns involved for the command to succeed. It
shouldn't depend on which path actually ends up being taken.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aaron Botsis | 2015-01-09 01:42:00 | Re: Patch: [BUGS] BUG #12320: json parsing with embedded double quotes |
| Previous Message | Josh Berkus | 2015-01-08 23:50:23 | Re: Turning recovery.conf into GUCs |