News for hackers. Stuff that matters.
Re:Upsert Lands in PostgreSQL 9.5 – A First Look by mbreese on Wednesday May 13, 2015 @12:19PM (#9540049)
The syntax looks inconvenient, but I like it. If you have a conflict, you might not want to just update everything, but only a subset of the fields. With this syntax (verbose as it is), you have the option of explicitly stating what you want to happen in the event of a conflict with no ambiguity. Perhaps there is a place for some shorthand like

    ON CONFLICT SET *=*.
But aside from that, for a RDBMS like Postgres, I'd opt for explicit over implicit.
Re:Upsert Lands in PostgreSQL 9.5 – A First Look by tracker1 on Wednesday May 13, 2015 @03:18PM (#9541310)
One would think you would just need a list of fields...

   ON CONFLICT SET colA,colB,colC
As to the gp, you don't want to update the "CREATED" field on an upsert.