目录
主要更新 (2)
mysql版本变更历史 (3)
5.0.67 (3)
5.0.77 (4)
5.1.2 (4)
5.1.38 (4)
5.1.4 (4)
5.1.41 (4)
5.1.42 (5)
File Format (5)
安装5.1.49 (7)
性能测试 (10)
主要更新
MySQL5.0从5.0.27以后，单数版本为社区版。双数版本号为企业版。
5.0.45我们现在使用的GA版
5.1.48最新的GA（Generally Available）版
5.5是Development版本
在下面的表格中，归纳了要求最迫切的特性，以及实施了这些特性或计划实施这些特性的版本：
特性MySQ系列
Foreign keys  3.23（针对InnoDB存储引擎）
Unions  4.0
Subqueries  4.1
R-trees  4.1（针对MyISAM存储引擎）
Stored procedures  5.0
Views  5.0
Cursors  5.0
XA transactions  5.0
Foreign keys  5.1（在3.23中实施，对于InnoDB）
Triggers  5.0和5.1
Full outer joins  5.1
Constraints  5.1（在3.23中实施，对于InnoDB）
Partitioning  5.1
Pluggable Storage Engine API5.1
Row-Based Replication  5.1
相关文章：
5.1的新功能：sql/doc/refman/5.1/en/mysql-nutshell.html
下面是一些介绍新功能的相关文章
MySQL5.1新特性之事件调度器(Event Scheduler)
MySQL5.1体验]MySQL分区
sql/tech-resources/articles/mysql_5.1_partitions.html
hu.edu.tw/MySQL/tech-resources/articles/mysql-events.html
innodb plugin
The InnoDB Plugin is available for MySQL5.1
New Features in the InnoDB Plugin
中文版innodb_plugin新特性
hi.baidu/unidba/blog/item/b6f02a0298a8dee708fa9331.html/cmtid/c1eeebd2c3e32 b0d3bf3cf6e
根据这篇文章
性能测试：
mysql版本变更历史
Changes in Release5.0.x(Production)
sql/doc/refman/5.0/en/news-5-0-x.html
Changes in Release5.1.x(Production)
sql/doc/refman/5.1/en/news-5-1-x.html
5.0.67
①The default value of the connect_timeout system variable was increased from5to10seconds. This might help in cases where clients frequently encounter errors of the form Lost connection to MySQL server at'XXX',system error:errno.(Bug#28359)
②The use of InnoDB hash indexes now can be controlled by setting the new innodb_adaptive_hash_index system variable at server startup.By default,this variable is enabled.See Section13.2.10.4,“Adaptive Hash Indexes”.
③Previously,index hints did not work for FULLTEXT searches.Now they work as follows:
For natural language mode searches,index hints are silently ignored.For example,IGNORE INDEX(i)is ignored with no warning and the index is still used.
For boolean mode searches,index hints are honored.(Bug#38842)
④Security Enhancement:To enable stricter control over the location from which user-defined functions can be loaded,the plugin_dir system variable has been backported from MySQL5.1.If the value is nonempty,user-defined function object files can be loaded only from the directory named by this variable.If the value is empty,the behavior that is used prior to the inclusion of plugin_dir applies:The UDF object files must be located in a directory that is searched by your system's dynamic linker.
If the plugin directory is writable by the server,it may be possible for a user to write executable code to a file in the directory INTO DUMPFILE.This can be prevented by making plugin_dir read only to the server or by setting--secure-file-priv to a directory where SELECT writes can be made safely.(Bug#37428)
5.0.77
A new status variable,Queries,indicates the number of statements executed by the server.This includes statements executed within stored programs,unlike the Questions variable which includes only statements sent to the server by clients.(Bug#41131)
5.1.2
mysql下载什么版本的
Added the bdb_cache_parts and bdb_region_size system variables,and permitted bdb_cache_size to be larger than4GB on systems that support it.(Bug#14895)
Added MAXLOCKS,MINLOCKS,MAXWRITE,and MINWRITE as allowable values of the --bdb-lock-detect option.(Bug#14876)
Added--replace to mysqldump.This option uses REPLACE INTO,rather than INSERT INTO,when writing the dumpfile.
5.1.38
正式将innodb_plugin加入到mysql中
5.1.4
增加mysqlslap，压力测试工具
官方文档
NoDBA博客上的一篇介绍性文章
另外一篇比较详细的攻略
5.1.41
sql/doc/refman/5.1/en/innodb-buffer-pool.html
innodb_old_blocks_pct and innodb_old_blocks_time are available as of MySQL 5.1.41,but only for InnoDB Plugin,not the built-in version of InnoDB.
5.0版本的innodb_buffer_pool也算法和下面的一样，区别在于新增加了两个选项，供用户进行调配。
InnoDB manages the pool as a list,using a least recently used(LRU) algorithm incorporating a midpoint insertion strategy.When room is
needed to add a new block to the pool,InnoDB evicts the least recently used block and adds the new
block to the middle of the list.The midpoint insertion strategy in effect causes the list to be treated as two sublists:
∙At the head,a sublist of“new”(or“young”)blocks that have been recently used.
∙At the tail,a sublist of“old”blocks that are less recently used. InnoDB now provides two system variables that enable LRU algorithm tuning:∙innodb_old_blocks_pct
Specifies the approximate percentage of the buffer pool used for
the old block sublist.The range of values is5to95.The default
value is37(that is,3/8of the pool).
∙innodb_old_blocks_time
Specifies how long in milliseconds(ms)a block inserted into the
old sublist must stay there after its first access before it can
be moved to the new sublist.The default value is0:A block inserted
into the old sublist moves immediately to the new sublist the first
time it is accessed,no matter how soon after insertion the access
occurs.If the value is greater than0,blocks remain in the old
sublist until an access occurs at least that many ms after the first
access.For example,a value of1000causes blocks to stay in the
old sublist for1second after the first access before they become
eligible to move to the new sublist.See Section7.5.5,“The
InnoDB Buffer Pool”
5.1.42
In this release,the InnoDB Plugin is included in source and binary distributions,except RHEL3, RHEL4,SuSE9(x86,x86_64,ia64),and generic Linux RPM packages.It also does not work for FreeBSD6and HP-UX or for Linux on S/390,PowerPC,and generic ia64.
当创建表等存在错误时，会提示error；否则mysql会自动做出一定的修改，使得满足条件，会给出warning
innodb_strict_mode=1目前也只有innodb_plugin支持该参数
File Format
关于Row Format的官方文档
sql/doc/innodb-plugin/1.1/en/innodb-row-format.html

版权声明：本站内容均来自互联网，仅供演示用，请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系QQ:729038198，我们将在24小时内删除。