Horton

Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}

Peter Geoghegan <pg@heroku.com>

View thread View on postgr.es
From: Peter Geoghegan <pg@heroku.com>
To: Andreas Karlsson <andreas@proxel.se>
Cc: Simon Riggs <simon@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Bruce Momjian <bruce@momjian.us>, Josh Berkus <josh@agliodbs.com>, Kevin Grittner <kgrittn@ymail.com>, Andres Freund <andres@2ndquadrant.com>, Heikki Linnakangas <hlinnakangas@vmware.com>, Pg Hackers <pgsql-hackers@postgresql.org>, Craig Ringer <craig@2ndquadrant.com>
Date: 2014-11-20T02:10:02Z
Lists: pgsql-hackers 
On Wed, Nov 19, 2014 at 6:04 PM, Peter Geoghegan <pg@heroku.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

Commits

  1. Change the way we mark tuples as frozen.

  2. Add documentation for data-modifying statements in WITH clauses.