There&#x27;s been a large migration off of mysql to postgres simply because Oracle got the rights to mysql when they purchased Sun. That is what made me <i>consider</i>, ditching mysql.<p>The final straw came when I stood up a mysql 5.6 instance to use as a data warehouse for about 5TB of data (15 billion rows). To my horror after spending a few weeks on this project I discovered that mysql only supported a small subset of the SQL language. Most of the needed sql features for data warehouse queries were simply not there (no WITH clause, no ROW_NUMBER(), only one sequence per table, no schema support, and many others that SQL report ninjas love to use)<p>With that I had to go back to management and convince them to put more time into the project so we could try again with postgresql. There was a large learning curve to go to postgres. It was just different in many areas, but at the same time, reminded me alot of IBM DB2 (both were a product of the 1980&#x27;s if you look at the history). Postgres fit into our plans nicely, it actually had a full blown intelligent query parser and optimizer unlike mysql. From what I learned, mysql&#x27;s purpose was to stop people from using text files as storage points in the early 2000&#x27;s. But once you graduate from that, it&#x27;s onward to postgres from there.