After having suffered with T SQL at MSFT for a number of years... yep, PostGres is almost always the best for almost any enterprise setup, despite what most other corpos seem to think.

Usually their reasons for not using it boil down to:

We would rather pay exorbitant licescing fees of some kind, forever, than rework a few APIs.

Those few APIs already having a fully compatible rewrite, done by me, working in test, prior to that meeting.

Gotta love corpo logic.

[–] msage@programming.dev 7 points 2 days ago

Yes, had those issues as well, though lately not a big corp, but mid-sized company.

One manager just wanted MySQL. We had trouble getting required performance from MySQL, when Postgres had good numbers. I had the app fully ready, just to be told no, you make it work in MySQL. So we dropped some 'useless stuff' like deferring flushing to disk and such.