3 ms·
Answering Q1: MySQL over Postgres. Postgres has 2 critical things going against it - The query optimizer is a mess - It's implementation of secondary indexes is
by pbhowmic 7y ago
Answering Q1: MySQL over Postgres. Postgres has 2 critical things going against it
- The query optimizer is a mess
- It's implementation of secondary indexes is not cache friendly, so it can be slow
- continuations 7y ago> implementation of secondary indexes is not cache friendly Can you get into more details about this? What about the implementation is not cache friendly?
- taffer 7y agoI don't know what you're trying to say. PostgreSQL makes no distinction between primary and secondary indexes. MySQL, which only knows clustered indexes (see "Unreasonable Defaults" [1]) has to make such a distinction, so that when you use a secondary index it also has to go through the primary index in addition to the secondary index. Also [1] https://use-the-index-luke.com/blog/2014-01/unreasonable-defaults-primary-key-clustering-key https://use-the-index-luke.com/blog/2014-01/unreasonable-def...