This is typical for how Postgres adds features and functionalities. They tend to add a new core feature in one release, then add adjacent functionality and performance improvements in later releases.
I'm not on their core developer mailing lists, but I presume this is because of a prioritization of stability over most everything else.