Request suggestion for a database between MySQL and Postgresql
PostgreSQL has a lot more modern SQL features compared to MySQL. 

Some of those featurese you might not find necessary right now but you'll deeply miss them once your application grows and your needs get more complex. Here are just some:


No check constraints
No deferrable constraints
No windowing functions
No common table expressions
No recursive queries (think hierarchical data)
Non transactional FK evaluation
No table functions
No function based index
No partial index
No full text search on transactional tables
No GIS features on transactional tables
Incomplete trigger implementation


Performance wise both will be pretty much the same (especially with such a tiny dataset). I wouldn't expect to see any difference between the two with your data.

If the database size grows, PostgreSQL seems to cope better with a lot of concurrent read and write access, while MySQL has some read optimizations that are not (yet) available in PostgreSQL (like index-only scans) which tends to make MySQL perform better in heavy read-only situations. But then every workload is different and it's basically impossible to generally say "one is faster than the other".

If you go for MySQL make sure you run it in ANSI and strict mode right from the beginning to get rid of some of gotchas that the default installation keeps for surprises (e.g. silently truncating data or accepting February 31st as a valid date).

(You might also want to look at the comment of ypercube here: https://stackoverflow.com/questions/9963012/what-does-the-sql-standard-say-about-dependent-conditionals-in-update/9963473#9963473 to get a feeling on what I mean with "gotchas")

This blog post also lists some of the really nice things about PostgreSQL (compared to SQL Server): 

http://facility9.com/2011/12/ten-reasons-postgresql-is-better-than-sql-server/