Since the end of 2000 (the 7.1 beta period), I'm an avid PostgreSQL user. All new projects I started were using PostgreSQL and I never had any issues with that

Since the end of 2000 (the 7.1 beta period), I'm an avid PostgreSQL user. All new projects I started were using PostgreSQL and I never had any issues with that configuration. Meanwhile, MySQL, which I had running for various third-party products like Wordpress, required some maintenance here and then, corrupted on-disk table files (and indexes), produced invalid dumps that were not restorable (and no warnings about that fact) and annoyed me with the inferior command line tool (better by now). One thing I wish PostgreSQL would add is to set a collation order on a specific index. Right now, in one of my applications, I can't rely on Postgres doing the sorting, forcing me to retrieve all rows and sort on the client side which is a) annoying and b) anything but fast. But whereas earlier, we had to set LC_COLLATE at initdb-time, now we can do it at createdb time and who knows - maybe we can do it at create index time in the future? I certainly lack the skill to contribute this particular feature.