The thing is that forking almost always hurts: you cannot easily get all new functionality from new versions of original product. Years pass - and your fork div

The thing is that forking almost always hurts: you cannot easily get all new functionality from new versions of original product. Years pass - and your fork diverge more and more from the origin. So it's much better to contribute to the original product. But it's not that easy if you change smth in core – code review in Postgres is very strict and hard. So back to the topic, adding extensible access methods now gives a lot of flexibility to Postgres Pro devs – I know that they have thing developed but not yet shipped to wide audience because before 9.6, that things could exist only as patches to Postgres. And nobody likes patches. Now it will be mere extensions.