| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Apply SELECT policies in INSERT/UPDATE+RETURNING |
| Date: | 2015-10-05 17:07:21 |
| Message-ID: | CAOuzzgrhd5mvNbA0yCqWOPR+_cwQRk-thLX0ZUN61h3MDNytjA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Peter,
On Monday, October 5, 2015, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Mon, Oct 5, 2015 at 4:55 AM, Stephen Frost <sfrost(at)snowman(dot)net
> <javascript:;>> wrote:
> > Apply SELECT policies in INSERT/UPDATE+RETURNING
>
> If we've changed this now, where does that leave the excluded.*
> pseudo-relation?
>
Away from my keyboard at the moment, and I'm sure Andres can comment, but I
didn't see this commit as changing anything regarding how excluded should
be handled (which Andres and I had at least seemed to come to an agreement
on).
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2015-10-05 17:38:45 | pgsql: docs: update guidelines on when to use GIN and GiST indexes |
| Previous Message | Peter Geoghegan | 2015-10-05 17:02:57 | Re: pgsql: Apply SELECT policies in INSERT/UPDATE+RETURNING |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2015-10-05 17:25:34 | Re: WIP: Rework access method interface |
| Previous Message | Peter Geoghegan | 2015-10-05 17:02:57 | Re: pgsql: Apply SELECT policies in INSERT/UPDATE+RETURNING |