What if MySQL fails to start after adding skip-innodb?

This article mainly explains "what to do when MySQL fails to start after adding skip-innodb". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn "what if MySQL fails to start after adding skip-innodb"!

On VPS with small memory, children's shoes (including me) generally like to do the so-called "optimization". In the optimization for MySQL, there are three parameters:

Skip-innodb / skip-bdb / skip-locking

In particular, the first parameter is said to save memory after opening it, so I filled in these three parameters in my.cnf after installing MySQL, but unfortunately, in the subsequent service mysqld restart, the startup failed. Is that all right?! So I hurriedly asked Google for advice, but sadly, under the current situation of "copying articles all over the world" on the domestic Internet, it was not easy to find an accurate answer through personal practice, and my problem was not solved in the end.

Later, I thought of taking a look at my MySQL version. I found a skip-external-locking parameter in my.cnf at the same time. After consulting Google, I learned that skip-external-locking is the new version of skip-locking,skip-locking. Moreover, in the new version of MySQL, the parameter skip-bdb has been abolished! At this point, the problem is basically solved. Now that skip-locking has changed, maybe skip-innodb has changed too! Finally, I found this sentence in the MySQLd document:

If InnoDB hasn't been built,the option-skip-innodb isn't available. We prefix with 'loose'to allow the option to be used at all times.

At this point, I believe you have a deeper understanding of "what to do when MySQL fails to start after adding skip-innodb". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!