{"push_id":672815639,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"631d7490074cdaef8026db57a5f2772b8730f600","before":"49ad32d5d99cb4a79bf648c0b7f9eca19b54cf1d","commits":[{"sha":"631d7490074cdaef8026db57a5f2772b8730f600","author":{"email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de","name":"Andres Freund"},"message":"Remove the new UPSERT command tag and use INSERT instead.\n\nPreviously, INSERT with ON CONFLICT DO UPDATE specified used a new\ncommand tag -- UPSERT.  It was introduced out of concern that INSERT as\na command tag would be a misrepresentation for ON CONFLICT DO UPDATE, as\nsome affected rows may actually have been updated.\n\nAlvaro Herrera noticed that the implementation of that new command tag\nwas incomplete; in subsequent discussion we concluded that having it\ndoesn't provide benefits that are in line with the compatibility breaks\nit requires.\n\nCatversion bump due to the removal of PlannedStmt->isUpsert.\n\nAuthor: Peter Geoghegan\nDiscussion: 20150520215816.GI5885@postgresql.org","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/631d7490074cdaef8026db57a5f2772b8730f600"}]}