Hacker News Reader

But the crappy codebases already exist outside of postgres anytime people have to roll their own upsert implementation.

The fact that it's hard is exactly why it should be in the database.

I don't think there's any contention at this point that it's a useful feature to have in the database. There just seems to be some disagreement on the finer points of the implementation. It'll get worked out, and Postgres will make it through another release with or without upsert.

Indeed, I followed the discussion and it was almost entirely about which implementation would best handle concurrency concerns.

Reply on news.ycombinator.com