Postgre SQL vs MySQL is of course loaded question. Both are robust applications and many times the choice of which to use is solely a matter of personal preference. Anyhow, both can be compared cheek to cheek in an attempt to help users decide which should be the right choice for them.
Here possibly PostgreSQL has the edge. MySQL never offers support to stored procedures, sub queries views, or cursors, which was potentially a serious mistake on the part of the MySQL developers. Although their claim is that these features are not required in a database development architecture. Anyways, you likely have to consider if you actually need the extra features in PostgreSQL database design in the first place, since developers in general really do not have any concrete use for them.
This term can of course have more than one meaning. As MySQL is much more extensively used many more applications provide support to it, and that also implies there is a wider community available to help and offer suggestions regarding problems you may face in daily use. PostgreSQL of course however has several active mailing lists and forums and there are some commercial concerns giving support services. Due to this, both applications are reasonably well-matched in this area.
Ease of use
This is a tough one. This is how a discussion among users of the two often goes – Person A: ‘Well MySQL is easier to use because’ then Person B immediately interrupts with “No, chump, PostgreSQL is much easier because” and the discussion revolves in circles. In fact just because Person A finds MySQL easier does not signify that Person B will and the same for PostgreSQL database design. This is in actual fact a matter of personal taste and new users may do well to try working a bit with each other to decide on their own which is the better choice
In press releases, MySQL claims to beyond just being stable, but the whisper over is that this is not entirely true. This may be partly due to the fact that certain features in recent upgrades to MySQL are till now “under construction” so as to say.
MySQL was designed to be a swift database, while PostgreSQL database design promotes itself as a more fully-featured application. However, both appear to be aspiring to meet somewhere in the middle with recent modifications and the difference in speed is almost like a nonissue.
The Final Word
Overall, it is apparent that there is no clear winner in this contest. So the new user should draw their own conclusions relying upon what best works for their specific needs and objectives.