这是我在mysql中的日志文件
2019-12-10 15:10:18 1428 InnoDB：警告：不建议使用innodb_additional_mem_pool_size。在将来的版本中，此选项可能与选项innodb_use_sys_malloc和InnoDB的内部内存分配器一起删除。 2019-12-10 15:10:18 5160 [Note] InnoDB：由于缓冲池较小，innodb_empty_free_list_algorithm已更改为旧版。为了使用退避，请将缓冲池至少增加到20MB。
2019-12-10 15:10:18 5160 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-12-10 15:10:18 5160 [Note] InnoDB: The InnoDB memory heap is disabled
2019-12-10 15:10:18 5160 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-12-10 15:10:18 5160 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-12-10 15:10:18 5160 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-12-10 15:10:18 5160 [Note] InnoDB: Using generic crc32 instructions
2019-12-10 15:10:18 5160 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-12-10 15:10:18 5160 [Note] InnoDB: Completed initialization of buffer pool
2019-12-10 15:10:18 5160 [Note] InnoDB: Highest supported file format is Barracuda.
2019-12-10 15:10:18 5160 [Note] InnoDB: Starting crash recovery from checkpoint LSN=7472761787
2019-12-10 15:10:19 5160 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2850 row operations to undo
InnoDB: Trx id counter is 1963520
2019-12-10 15:10:19 5160 [Note] InnoDB: Starting final batch to recover 307 pages from redo log
答案 0 :(得分：0)
警告：不建议使用innodb_additional_mem_pool_size。在将来的发行版中，此选项可能与选项innodb_use_sys_malloc和InnoDB的内部内存分配器一起删除。
根据 https://blogs.oracle.com/supportingmysql/entry/remove_on_sight_thread_concurrency ，MySQL 5.6将在配置文件中弃用三个参数：
thread_concurrency innodb_additional_mem_pool_size innodb_use_sys_malloc
解决方案： 如果当前使用的是5.1或5.5版本，建议将参数值设置为1 innodb_use_sys_malloc = 1 如果是5.6.3版或更高版本，请注释参数： innodb_additional_mem_pool_size
答案 1 :(得分：0)
从c：xampp \ mysql \ data目录删除ibdata1文件ib_logfile1，ib_logfile1后，它开始工作