The thing is I wasn't trying to convince anyone though :) I doubt anyone here will be willing to shell out the money for a license. Although, Azure might make it affordable but I hated the limitations they put on the mssql instances (can't remember them rn).
My biggest problem with myssql is that it is very immature. Biggest problems I have with it are (right now, b/c that's what I'm facing atm): transaction isolation and stored procedures. I'm pretty sure pg has the same lame transaction isolation issues as well.
Whatever transaction isolation issues PostgreSQL might have, I guarantee you it doesn't have the "same lame" ones as MySQL.
As just one example: "range locking". Look it up.
the biggest one for me is the lack of support for nested transactions
Which you can effectively accomplish in PostgreSQL with SAVEPOINTs. In fact, with those, you can have arbitrarily complicated nesting of "transactions", though that does start to smell a bit like a foot-gun pretty quickly.
http://www.postgresql.org/docs/current/static/sql-savepoint....
Re:Announcing SQL Server on Linux
by vertex-four on Tuesday March 08, 2016 @07:19AM
(#11244804)
What do you mean Postgres has tx isolation issues? The entire point of preferring it over mySQL is that it does most things around that area properly.
Well, gosh. I'm convinced.
(Full disclosure: I abhor MySQL. But if you're paying attention, you'll notice that my position is a statement of opinion, while yours is a statement of "fact". The reality is, every RDBMS has strengths and weaknesses, and should be evaluated for their applicability to a given project on a case-by-case basis — at which point, I'm sure, you'll conclude that PostgreSQL is the best choice, anyway.) ;)