mysql报错级别_MySQL启动出现几个警告级别错误
日志如下2015-03-2720:45:324876[Note]InnoDB:Usingatomicstorefcountbufferpoolpages2015-03-2720:45:324876[Note]InnoDB:TheInnoDBmemoryheapisdisabled2015-03-2720:45:324876[Not...
日志如下
2015-03-27 20:45:32 4876 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-03-27 20:45:32 4876 [Note] InnoDB: The InnoDB memory heap is disabled
2015-03-27 20:45:32 4876 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-03-27 20:45:32 4876 [Note] InnoDB: Memory barrier is not used
2015-03-27 20:45:32 4876 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-03-27 20:45:32 4876 [Note] InnoDB: Not using CPU crc32 instructions
2015-03-27 20:45:32 4876 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-03-27 20:45:32 4876 [Note] InnoDB: Completed initialization of buffer pool
2015-03-27 20:45:32 4876 [Note] InnoDB: Highest supported file format is Barracuda.
2015-03-27 20:45:32 4876 [Note] InnoDB: 128 rollback segment(s) are active.
2015-03-27 20:45:32 4876 [Note] InnoDB: Waiting for purge to start
2015-03-27 20:45:32 4876 [Note] InnoDB: 5.6.21 started; log sequence number 1600607
2015-03-27 20:45:32 4876 [Note] Server hostname (bind-address): '*'; port: 3306
2015-03-27 20:45:32 4876 [Note] IPv6 is available.
2015-03-27 20:45:32 4876 [Note] - '::' resolves to '::';
2015-03-27 20:45:32 4876 [Note] Server socket created on IP: '::'.
解決了好久就是不知道為什么
展開
總結
以上是生活随笔為你收集整理的mysql报错级别_MySQL启动出现几个警告级别错误的全部內容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: 深拷贝的缺点_拷贝?还傻傻分不清深浅?
- 下一篇: mysql+linux+无法启动服务无法