> olavgg: Use multi-column/functional/partial indexes, as this will help you design a database where most of your 'hot' indexes can fit in RAM. If you have too many indexes, you will do index scan on disk, which is painfully slow. I[n] many cases a full table scan (sequential read) would be faster instead.
How far can you go with MySQL or MariaDB? | https://news.ycombinator.com/item?id=14892184 (Aug 2017)
> dmux This is a great resource RE indexing: http://use-the-index-luke.com/
There is a detailed PostgreSQL optimization comment there that may be more what you had in mind:
https://news.ycombinator.com/item?id=14896154
> olavgg: Use multi-column/functional/partial indexes, as this will help you design a database where most of your 'hot' indexes can fit in RAM. If you have too many indexes, you will do index scan on disk, which is painfully slow. I[n] many cases a full table scan (sequential read) would be faster instead.