EnterpriseDB (which started this project) specializes in providing postgresql version that can emulate most of Oracle database functionality, so this is not surprising.
Anyway maybe I should say differently, maybe they don't provide most of the functionality, but their goal is provide database that can help to migrate away from Oracle, and this storage engine that appears to mimic one in Oracle (and I'm guessing has similar tradeoffs) fits that model.
What is the basis for this statement?
* MATCH_RECOGNIZE isn't supported
* reference partitions aren't supported
* TIMESTAMP is incompatible and the default compile options are comically bad
These are the first three things that came to mind and none of them are supported so I stopped looking further.