Horton

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

Heikki Linnakangas <hlinnakangas@vmware.com>

View thread View on postgr.es
From: Heikki Linnakangas <hlinnakangas@vmware.com>
To: Kevin Grittner <kgrittn@ymail.com>, Peter Geoghegan <pg@heroku.com>
Cc: Jeff Janes <jeff.janes@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Josh Berkus <josh@agliodbs.com>, Craig Ringer <craig@2ndquadrant.com>, Anssi Kääriäinen <anssi.kaariainen@thl.fi>, "Simon Riggs" <simon@2ndquadrant.com>, Bruce Momjian <bruce@momjian.us>, "Andres Freund" <andres@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2014-12-18T15:51:35Z
Lists: pgsql-hackers 
On 12/18/2014 05:46 PM, Kevin Grittner wrote:
> I don't think either point was ever really settled beyond Robert
> and I preferring ON DUPLICATE versus Peter preferring ON CONFLICT.

I also prefer ON CONFLICT, because that makes more sense when you 
consider exclusion constraints, which I'm still hoping that this would 
support. If not immediately, at least in the future.

- Heikki

Commits

  1. Change the way we mark tuples as frozen.

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