Hacker News new | ask | show | jobs
by koolba 3383 days ago
And the Oracle compatibility piece breaks so much that it would never get merged into community Postgres.
2 comments

Even if it didn't, for all the work they put into the community version one can't begrudge them trying to make a living on the enterprise side.
There are also plenty of devs in the community, outside the EnterpriseDB employees, who do do not want to pollute core PostgreSQL with alternative ways to do things it already can do just because of Oracle compatibility. Aliases have been added for ISO SQL compatibility, but adding features purely (i.e. features with zero value unless you are migrating from Oracle) for Oracle compatibility is not something core PostgreSQL does.