PostgreSQL's MVCC is bad. So is everyone else's
masklinn
33 points
20 comments
July 29, 2026
Related Discussions
Found 5 related stories in 333.6ms across 15,380 title embeddings via pgvector HNSW
- PostgreSQL's MVCC is bad. So is everyone else's radimm · 17 pts · July 28, 2026 · 100% similar
- PostgreSQL is enough (2024) Imustaskforhelp · 103 pts · June 24, 2026 · 55% similar
- Better JIT for Postgres vladich · 143 pts · March 04, 2026 · 55% similar
- PostgreSQL and the OOM killer: Why we use strict memory overcommit furkansahin · 166 pts · July 03, 2026 · 51% similar
- PostgreSQL 19 features I'm excited about tianzhou · 34 pts · April 30, 2026 · 50% similar
Discussion Highlights (5 comments)
jhgb
I'm surprised that Interbase/Firebird seems to be entirely omitted from this despite pioneering the MVCC approach.
gtowey
I'm conflicted with this article. It does pack a lot of good information in there, and it's a useful comparison of the core difference between PostgreSQL and MySQL. But it still contains a lot of LLM-isms which are off putting and make me want to stop reading when I see them.
shayonj
> Nothing was solved. The four questions got new answers, and the costs moved into the compactor. I have been meaning to write on this topic and in relation to LSM for a while. So, I appreciated that note on LSMs. There are no free ~lunches~ reads or writes.
evanelias
Dupe of https://news.ycombinator.com/item?id=49078196 which was posted a couple days ago, and then seemingly revived in second chance pool before getting flagged for obvious slop-tone.
radimm
OP, here thank you for comments and while I might not like it to be called LLM - I give up.