MySQL5.1.48后可能会导致crash的bug
来源:互联网 发布:腾讯云数据库问题 编辑:程序博客网 时间:2024/06/10 20:10
从48往后的版本的changelog中收集,还没细看,先整理下来!
------------------------------------------------------------------------------------------------------------------
fixed in 5.1.49:
Bug#50364
Replication: FLUSH LOGS could in some circumstances crash the server. This occurred because the I/O thread could concurrently access the relay log I/O cache while another thread was performing the FLUSH LOGS, which closes and reopens the relay log and, while doing so, initializes (or re-initializes) its I/O cache. This could cause problems if some other thread (in this case, the I/O thread) is accessing it at the same time. Now the thread performing the FLUSH LOGS takes a lock on the relay log before actually flushing it
Bug#54041
A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data.
Bug#42064
The server could crash with an out of memory error when trying to parse a query that was too long to fit in memory. Now the parser rejects such queries with an ER_OUT_OF_RESOURCES error.
fiexed in 5.1.50:
Bug#55581
The server could crash on shutdown, if started with --innodb-use-system-malloc=0.
Bug#54453
The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.)
Bug#54408
The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT.
Bug#54041
A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data.
fiexed in 5.1.51:
Bug#46086
Partitioning: When the storage engine used to create a partitioned table was disabled, attempting to drop the table caused the server to crash.
fiexed in 5.1.55
Bug#58553
Issuing EXPLAIN EXTENDED for a query that would use condition pushdown could cause mysqld to crash.
Bug#58396
EXPLAIN could crash for queries that used GROUP_CONCAT().
Bug#57703
Unnecessary subquery evaluation in contexts such as statement preparation or view creation could cause a server crash.
Bug#57321
NULL geometry values could cause a crash in Item_func_spatial_collection::fix_length_and_dec.
Bug#51817
When mysqld printed crash dump information, it incorrectly indicated that some valid pointers were invalid
- MySQL5.1.48后可能会导致crash的bug
- [BUG]按Home键切换到后台后会触发libGPUSupportMercury.dylib: gpus_ReturnNotPermittedKillClient导致crash
- [MySQL Bug] 在RBR复制模式下使用Merge引擎导致备库Crash的bug
- VS2010中删除某些不用的控件后可能会导致资源视图打不开
- implicit declaration 导致的crash
- RapidXML 导致的 crash 问题
- 使用coredata导致的版本更新后程序crash的问题
- 使用coredata导致的版本更新后程序crash的问题
- 使用coredata导致的版本更新后程序crash的问题
- ThreadLocal的误用可能会导致OutOfMemoryError
- 又见bug,动态调整SGA参数导致数据库crash
- JSONKit 解析后存在NSULL对象导致的Crash问题处理
- 混淆后的程序Monkey测试出现crash如何进行改Bug
- if导致的bug
- snprintf 导致的bug
- 粗心导致的bug
- munmap导致的BUG
- Solaris 64bit (Sparc) 平台下,oracle 软件的bug ,实例启动248天会导致 db 或者asm crash
- 有关chrome插件开发(自己看了一下,觉得很有意思)
- Android4: 请放弃使用Theme.Dialog
- 内存数据库H2 初次探索
- 深入浅出---unix多进程编程之wait()和waitpid()函数
- 国庆学WP7系列第三季--Windows Phone 7 Series Developer General FAQ(译)
- MySQL5.1.48后可能会导致crash的bug
- PHP变量的声明和使用
- strust2中关于一些信息提示 Error 、 FieldError、 ActionMessage整理笔记
- Android游戏框架AndEngine使用入门
- 从excel中一列截取从右或者右开始的指定字符串
- Faced.me:基于面部识别的互粉社交移动应用(视频)
- MongoDB安装Windows服务
- 5 个 Ajax 最佳实践
- 动态规划算法