I'd also add that if it's a community-based open source project, there can be great benefit in more safely supporting a bigger set of database engines (e.g. sqlite for the simple entry-level, postgres et al for the more serious) at the cost of some performance overhead.

If it's a performance-critical in-house service where you have full control of the deployment and can tailor it to your use-case, it's a completely different story.