1. It takes a while to get widespread agreement on the semantics to make sure it really solves the problem in a comprehensive way.
2. The existing mechanism is "good enough", so nobody is quite experiencing enough pain that they dedicate the effort to solve it.
These aren't great reasons, because other databases have had partitioning features for a long time. But they are reasons.
that is actually why i wrote the partitioned gem (which this explanation is apart of): https://github.com/fiksu/partitioned the lack of automatic table management is pretty painful and the gem helps you manage such things.
there is some support for redshift also: https://github.com/fiksu/activerecord-redshift-adapter
(this is all for rails)
The problem happens when this B-tree is too large to fit into your working memory: swapping parts of the B-tree in and out of memory repeatedly to answer a query is very slow. The solution that partitioning offers is to allow you to split your indexes (and your data) so that, depending on your access-patterns you could see less swapping of that index.
A thing I can't understand is why this isn't made automatic.
If there are 100 companies, you don't want to create 100 tables, then add 100 FOREIGN KEY constrains, and then again each time a new company appears, do you? Wouldn't a "syntactic sugar" like "PARTITION BY company_id" that does all this automatically be possible?
Just asking if there is a reason something like this is not implemented.