Proper transactions, like the ones that aren't closed by create, alter or drop table, proper rollbacks, statement timeouts so that a single stalled statement do

Proper transactions, like the ones that aren't closed by create, alter or drop table, proper rollbacks, statement timeouts so that a single stalled statement doesn't block the table until you kill it, subscribe/notify among other things. My issue is primarily with performance under load, where you'll eventually end up with lots of blocked queries and an unresponsive database and the only way to solve it is to throw hardware resources at it. Do yourselvs a favour and pick Postgres for new projects. If you properly vacuum your tables you'll probably be fine.