Earlier quoted context omitted.
MySQL and Postgres have multi-master replication. They do NOT have distributed transactions (with the distributed locking system etc). For some customers it is important. Others have delusions that they need it. Oracle has other products as well. I am generally aware of couple used widely. Their ESB is one of the heavy players, and some sausage stands always need the most advanced ones. The funny thing is that with O…
Postgres has two-phase commit, which can be used at the application level to implement distributed transactions. It does not have multi-master replication natively, though there are companion projects that enable it.
Adding extra implementation to application, to do the database's work against the usual division of labor, no thanks. And bringing some shady 3rd party support package on top of the database is a second really big no.
For businesses only what you get out of the box counts. Otherwise you can always state that "the platform has C++ compiler, stfu and code". That doesn't really work. The companies are into buying complete products for a reason: they don't want to implement unnecessarily things they really should just get out of the box.
TBH I love postgres, but before they offer proper multi-master transactions out of the box most companies just still go for Oracle. That's similar as to why people buy Photoshop. GIMP fell some 10 years after in usability and features when they did not prioritize implementing the dynamic layer effect system. Instead of that they chose to masturbate with GEGL or something like that for 10 years, without providing the actual end user requested features. The situation still stands there, before they implement what Photoshop 4 or so did they got no chance of being valid alternative...