Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Peter Geoghegan <pg@heroku.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Heikki Linnakangas <hlinnakangas@vmware.com>, Martijn van Oosterhout <kleptog@svana.org>, Jeff Janes <jeff.janes@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>, Kevin Grittner <kgrittn@ymail.com>, Andres Freund <andres@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2014-12-23T19:36:33Z
Lists: pgsql-hackers
* Peter Geoghegan (pg@heroku.com) wrote: > On Tue, Dec 23, 2014 at 5:46 AM, Robert Haas <robertmhaas@gmail.com> wrote: > > On Mon, Dec 22, 2014 at 5:04 PM, Peter Geoghegan <pg@heroku.com> wrote: > >> If you're dead set on having an escape hatch, maybe we should just get > >> over it and add a way of specifying a unique index by name. As I said, > >> these under-served use cases are either exceedingly rare or entirely > >> theoretical. > > > > I'm decidedly unenthusiastic about that. People don't expect CREATE > > INDEX CONCURRENTLY + DROP INDEX CONCURRENTLY to break their DML. I > > think the solution in this case would be a gateway to problems larger > > than the one we're trying to solve. > > I tend to agree. I think we should just live with the fact that not > every conceivable use case will be covered, at least initially. Then, > if an appreciable demand for even more flexibility emerges, we can > revisit this. We already have a syntax that is significantly more > flexible than the equivalent feature in any other system. Let's not > lose sight of that. +1 Thanks, Stephen
Commits
-
Change the way we mark tuples as frozen.
- 37484ad2aace 9.4.0 cited
-
Add documentation for data-modifying statements in WITH clauses.
- 0ef0b3020402 9.1.0 cited