If all you care about is QPS, by all means, stick with MySQL.<p>People like myself use Postgres because it has a much richer feature set.  See <a href="http:&#x2F;&#x2F;stackoverflow.com&#x2F;a&#x2F;5023936&#x2F;270610" rel="nofollow">http:&#x2F;&#x2F;stackoverflow.com&#x2F;a&#x2F;5023936&#x2F;270610</a> for some examples.  Personally I find MySQL beyond frustrating due to its lack of… well almost all of those.  Recursive CTEs in particular, but arrays and rich indexing are pretty core too.<p>Postgres&#x27;s query optimizer is far more advanced too.  MySQL doesn&#x27;t even optimize across views, which discourages good coding practices.<p>The documentation is fantastic.  Complete and well-written, covers the nuances of every command, expression, and type.  MySQL&#x27;s doesn&#x27;t hold a candle to it.<p>Don&#x27;t know what you mean about &quot;unfriendly&quot;.  Help is built into the command-line tool, and like I said, the documentation is fantastic.  Maybe MySQL is a little more &quot;hand-holdy&quot;, but I don&#x27;t care for such things so I wouldn&#x27;t know.