| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andreas Karlsson <andreas(at)proxel(dot)se> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Subject: | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |
| Date: | 2014-11-20 02:10:02 |
| Message-ID: | CAM3SWZTjpDN5C9okmGs2vhK1WcT06Pu0ePmqsYfaZDZgkBtkkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 19, 2014 at 6:04 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> I think that 3 is out. It seems hard to justify not RETURNING anything
> in respect of a slot when there is a before row insert trigger that
> returns NULL on the one hand, but RETURNING something despite not
> inserting for ON CONFLICT UPDATE on the other.
I mean: despite not inserting *or updating*.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-11-20 02:17:30 | Re: New Event Trigger: table_rewrite |
| Previous Message | Peter Geoghegan | 2014-11-20 02:04:18 | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |