- C.2 Changes in Release 5.1.x (Production)
- C.2.1 Changes in MySQL 5.1.39 (Not yet released)
- C.2.2 Changes in MySQL 5.1.38 (01 September 2009)
- C.2.3 Changes in MySQL 5.1.37 (13 July 2009)
- C.2.4 Changes in MySQL 5.1.36 (16 June 2009)
- C.2.5 Changes in MySQL 5.1.35 (13 May 2009)
- C.2.6 Release Notes for MySQL Enterprise 5.1.34sp1 [QSP] (25 June 2009)
- C.2.7 Changes in MySQL 5.1.34 (02 April 2009)
- C.2.8 Changes in MySQL 5.1.33 (13 March 2009)
- C.2.9 Changes in MySQL 5.1.32 (14 February 2009)
- C.2.10 Release Notes for MySQL Enterprise 5.1.31sp1 [QSP] (19 March 2009)
- C.2.11 Changes in MySQL 5.1.31 (19 January 2009)
- C.2.12 Changes in MySQL 5.1.30 (14 November 2008 General Availability)
- C.2.13 Changes in MySQL 5.1.29 (11 October 2008)
- C.2.14 Changes in MySQL 5.1.28 (28 August 2008)
- C.2.15 Changes in MySQL 5.1.27 (Not released)
- C.2.16 Changes in MySQL 5.1.26 (30 June 2008)
- C.2.17 Changes in MySQL 5.1.25 (28 May 2008)
- C.2.18 Changes in MySQL 5.1.24 (08 April 2008)
- C.2.19 Changes in MySQL 5.1.23 (29 January 2008)
- C.2.20 Changes in MySQL 5.1.22 (24 September 2007 Release Candidate)
- C.2.21 Changes in MySQL 5.1.21 (16 August 2007)
- C.2.22 Changes in MySQL 5.1.20 (25 June 2007)
- C.2.23 Changes in MySQL 5.1.19 (25 May 2007)
- C.2.24 Changes in MySQL 5.1.18 (08 May 2007)
- C.2.25 Changes in MySQL 5.1.17 (04 April 2007)
- C.2.26 Changes in MySQL 5.1.16 (26 February 2007)
- C.2.27 Changes in MySQL 5.1.15 (25 January 2007)
- C.2.28 Changes in MySQL 5.1.14 (05 December 2006)
- C.2.29 Changes in MySQL 5.1.13 (Not released)
- C.2.30 Changes in MySQL 5.1.12 (24 October 2006)
- C.2.31 Changes in MySQL 5.1.11 (26 May 2006)
- C.2.32 Changes in MySQL 5.1.10 (Not released)
- C.2.33 Changes in MySQL 5.1.9 (12 April 2006)
- C.2.34 Changes in MySQL 5.1.8 (Not released)
- C.2.35 Changes in MySQL 5.1.7 (27 February 2006)
- C.2.36 Changes in MySQL 5.1.6 (01 February 2006)
- C.2.37 Changes in MySQL 5.1.5 (10 January 2006)
- C.2.38 Changes in MySQL 5.1.4 (21 December 2005)
- C.2.39 Changes in MySQL 5.1.3 (29 November 2005)
- C.2.40 Changes in MySQL 5.1.2 (Not released)
- C.2.41 Changes in MySQL 5.1.1 (Not released)
This is a Service Pack release of the MySQL Enterprise Server 5.1.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.1.34).
Note
The fix for Bug#40974 in MySQL 5.1.31 caused the regression problem reported in Bug#44810. Users for whom stability is of utmost priority should note that 5.1.34sp1 is affected by this problem because Bug#44810 is not fixed until MySQL 5.1.36.
If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Bugs fixed:
Incomplete cleanup of
JOIN_TAB::selectduring the filesort of rows for aGROUP BYclause inside a subquery caused a server crash. (Bug#44290)Use of
HANDLERstatements withINFORMATION_SCHEMAtables caused a server crash. NowHANDLERis prohibited with such tables. (Bug#44151)On 64-bit systems, a
key_buffer_sizevalue larger than 4GB could couseMyISAMindex corruption. (Bug#43932)On Windows, a server crash occurred for attempts to insert a floating-point value into a
CHARcolumn with a maximum length less than the converted floating-point value length. (Bug#43833)libmysqldcrashed when it was reinitialized. (Bug#43706, Bug#44091)Certain statements might open a table and then wait for an impending global read lock without noticing whether they hold a table being waiting for by the global read lock, causing a hang. Affected statements are
SELECT ... FOR UPDATE,LOCK TABLES ... WRITE,TRUNCATE TABLE, andLOAD DATA INFILE. (Bug#43230)-
Using an XML function such as
ExtractValue()more than once in a single query could produce erroneous results. (Bug#43183)See also Bug#43937.
Incorrect elevation of warning messages to error messages for unsafe statements caused a server crash. (Bug#42640)
In an
UPDATEorDELETEvia a secondary index,InnoDBdid not store the cursor position. This madeInnoDBcrash in semi-consistent read while attempting to unlock a nonmatching record. (Bug#39320)-
The functions listed in Section 11.13.4.2.3, “Creating Geometry Values Using MySQL-Specific Functions”, previously accepted WKB arguments and returned WKB values. They now accept WKB or geometry arguments and return geometry values.
The functions listed in Section 11.13.4.2.2, “Creating Geometry Values Using WKB Functions”, previously accepted WKB arguments and returned geometry values. They now accept WKB or geometry arguments and return geometry values. (Bug#38990)
User Comments
Add your own comment.