> Hi Johannes! Thanks for taking the time to reach out. I'm struggling > to understand what the "bug" is. Config files that have been customized > have to be manually updated in any major upgrade. I don't think that's > specific to MySQL.
Hi Clint, good question. It bugged me, because I did not get any log entries under /var/log/mysql*, so I had to start mysqld in a way I usually don't, in order to get a diagnostic message about what was going on. Also, as far as I can remember I never introduced the option skip-bdb manually. For me, if a previously valid configuration option makes a service fail to start after the upgrade, this is unexpected. But I do not want to complain, I added this information to help others to solve the problem! If the maintainers get something out of it, even better.
