I think it's a bad idea to evaluate by checklists of features you think you need. It's kind of like choosing where to live based on a checklist. I started with

I think it's a bad idea to evaluate by checklists of features you think you need. It's kind of like choosing where to live based on a checklist. I started with MySQL, then used MySQL and PostgreSQL for a while. Then, when I started to do more "real" projects, I just got so frustrated with MySQL in so many ways at once. It wasn't that MySQL couldn't do it, it's that it was frustrating at every turn. In my case, what caused me to drop MySQL almost entirely (around 2003 or 2004) was doing a few simple reports involving dates. Then I started using postgres and it was refreshingly consistent and flexible without so many caveats. And now I develop for postgresql, and the code is similarly consistent and flexible (and just all-around nice). I have had a long string of positive experiences with postgres. It's hard to wrap them up into a feature checklist. If something held you back from using postgres in the past, it's a good idea to watch the release notes to see if something new might solve that problem (or better yet, discuss on the lists so maybe it will be solved faster). But I tend to think that looking at long lists of features is a distraction.