I guess we can have this discussion forever and ever, but you won't convince me that HSQLDB that is written by one (or maybe two) persons and was released six years ago is a better piece of software than PostgreSQL, that has been worked on for the last twenty years by all these people:
http://www.postgresql.org/community/contributors/The fact that people keep reporting database crashes on the forum is enough for me. A good database is written to handle unplanned shutdowns, power outages etc. At worst, the last seconds of written data should not be commited. A database that goes totally corrupt, even on rare occasions, is useless for production code. Try selling that to a bank or a hospital?
I agree with MadEvil on doing backups, but only because hardware fails. And maybe because I sometimes write crappy code and then it's good having a backup to go back to.
