测试了下，在没加skip-innodb时，删除了这三个文件，启动时会自动创建这三个文件，日志如下： 引用 InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 090613 10:19:37 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 090613 10:19:37 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 24 MB InnoDB: Database physically writes the file full: wait... 090613 10:19:38 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 24 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 090613 10:19:39 InnoDB: Started; log sequence number 0 0 090613 10:19:39 [Note] C:/www/mysql/bin/mysqld-nt: ready for connections.
再删除这三个文件，加了skip-innodb后，启动日志： 引用
090613 10:30:12 [Note] C:/www/mysql/bin/mysqld-nt: Normal shutdown
090613 10:30:17 [Note] C:/www/mysql/bin/mysqld-nt: ready for connections. Version: '5.0.45' socket: '' port: 3306 Source distribution
那三个文件就不会自动产生了。
您可能感兴趣的文章:
Windows 64 位 mysql 5.7以上版本包解压中没有data目录和my-default.ini及服务无法启动的快速解决办法(问题小结)Linux下MySQL5.7.18二进制包安装教程（无默认配置文件my_default.cnf）MySQL 5.6 中的 TIMESTAMP 和 explicit_defaults_for_timestamp 参数MySQL 5.6 中TIMESTAMP with implicit DEFAULT value is deprecated错误MySQL之Field‘***’doesn’t have a default value错误解决办法解决Default storage engine (InnoDB) is not available导致mysql无法启动的修改办法详解MySQL中default的使用
