zlacker

>>andren+(OP)
This post has a valid point. But the last line makes it clear why they care so much about it.

Yeah, table bloat and transaction ID wraparounds are terrible, but easily avoidable if you follow a few simple guidelines. Typically in my experience, best way to avoid these issues are to set sensible vacuum settings and track long running queries.

I do hate the some of the defaults in the Postgres configuration are too conservative for most workloads.

>>sppras+Ul
Paying an overhead cost of 53 bytes per row is also too expensive for MVCC in my opinion.