Andres Freund 631d749007 Remove the new UPSERT command tag and use INSERT instead. ... Previously, INSERT with ON CONFLICT DO UPDATE specified used a new command tag -- UPSERT. It was introduced out of concern that INSERT as a command tag would be a misrepresentation for ON CONFLICT DO UPDATE, as some affected rows may actually have been updated. Alvaro Herrera noticed that the implementation of that new command tag was incomplete; in subsequent discussion we concluded that having it doesn't provide benefits that are in line with the compatibility breaks it requires. Catversion bump due to the removal of PlannedStmt->isUpsert. Author: Peter Geoghegan Discussion: 20150520215816.GI5885@postgresql.org		2015-05-23 00:58:45 +02:00
..
src	Remove the new UPSERT command tag and use INSERT instead.	2015-05-23 00:58:45 +02:00
bug.template	Stamp HEAD as 9.5devel.	2014-06-10 21:36:13 -04:00
KNOWN_BUGS
Makefile
MISSING_FEATURES
TODO