Hacker News Reader

> not throwing any effort into postgresql

The amount of research about the on-disk internals of both PostgreSQL and MySQL are a lot more effort than I would have probably spent (granted, I don't have a team of highly paid devs at my disposal, but still, I've seen technical decisions made on the basis of Google Trends...).

View on HN

In my personal opinion, those bits of research aren't much, and they would have found it when they looked around for the cause of the write-amplification. A truly good amount of research would also have popped up heap-only-tuples, as mentioned here[0], or other ways to mitigate too many secondary-index updates.

0: https://news.ycombinator.com/item?id=12167161

It is not much effort to understanding the storage of each database. It is like a common sense for database guys.

Reply on news.ycombinator.com