TGViewer
CatOps CatOps @catops · 5.09K subscribers
Post #2967 1.3K
A great article about Postgres' MVCC, or rather, issues with MVCC and the ways other engines tried to mitigate those.

It has a neat comparison of the tradeoffs, strong and weak parts of different implementations. It also provides insights into how different DB engines work.

A quote:

... if someone tells you a database has solved multi-versioning, ask them the four questions: where do old versions live, which way do chains point, what do indexes point at, and who cleans up. Then ask what happens when a transaction stays open over lunch.

#postgres #databases
boringSQL | Supercharge your SQL & PostgreSQL powers PostgreSQL's MVCC is bad. So is everyone else's. The critics are right: PostgreSQL's MVCC bloats tables and amplifies writes. Oracle, InnoDB, SQL Server, MongoDB, LSM stores, and etcd answer the same four design questions differently, and each pays for it somewhere else.
  • ❤ 3
More from @catops
  1. Sep 28, 2026​​For today’s Donations Monday, I’d like to remind you about a fundraiser for a pickup tru…
  2. Sep 26, 2026Here’s Datadog’s take on the increased load on CI. In this article they explain how their…
  3. Sep 25, 2026A new chapter of the CatOps Digest is here! https://newsletter.catops.dev/p/catops-digest-…
  4. Sep 24, 2026Shopify wrote an article on them moving from React Native to the native code for their mob…
  5. Sep 23, 2026A bunch of practice exams on Humble Bundle, if you're into this type of thing. This offer…
  6. Sep 21, 2026​​A good friend of the channel raises funds for his new unit (a small air defense unit). T…
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →