> as of 2017 at least the plan was to implement merge using the underlying insert on conflict mechanism That was something that was discussed at length at the

> as of 2017 at least the plan was to implement merge using the underlying insert on conflict mechanism That was something that was discussed at length at the time, but ultimately rejected. And so the implementation of MERGE in Postgres has essentially the same limitations as every other MERGE implementation that I'm familiar with. Postgres clearly stresses the trade-off that MERGE makes in the docs, though. Which probably sets it apart.