- D.1 Changes in Release 5.1.x (Production)
- D.1.1 Changes in MySQL 5.1.64 (Not yet released)
- D.1.2 Changes in MySQL 5.1.63 (07 May 2012)
- D.1.3 Changes in MySQL 5.1.62 (21 March 2012)
- D.1.4 Changes in MySQL 5.1.61 (10 January 2012)
- D.1.5 Changes in MySQL 5.1.60 (16 November 2011)
- D.1.6 Changes in MySQL 5.1.59 (15 September 2011)
- D.1.7 Changes in MySQL 5.1.58 (05 July 2011)
- D.1.8 Changes in MySQL 5.1.57 (05 May 2011)
- D.1.9 Changes in MySQL 5.1.56 (01 March 2011)
- D.1.10 Changes in MySQL 5.1.55 (07 February 2011)
- D.1.11 Changes in MySQL 5.1.54 (26 November 2010)
- D.1.12 Changes in MySQL 5.1.53 (03 November 2010)
- D.1.13 Changes in MySQL Enterprise 5.1.52sp1 [QSP] (21 February 2011)
- D.1.14 Changes in MySQL 5.1.52 (11 October 2010)
- D.1.15 Changes in MySQL 5.1.51 (10 September 2010)
- D.1.16 Changes in MySQL 5.1.50 (03 August 2010)
- D.1.17 Changes in MySQL Enterprise 5.1.49sp1 [QSP] (28 September 2010)
- D.1.18 Changes in MySQL 5.1.49 (09 July 2010)
- D.1.19 Changes in MySQL 5.1.48 (02 June 2010)
- D.1.20 Changes in MySQL 5.1.47 (06 May 2010)
- D.1.21 Changes in MySQL Enterprise 5.1.46sp1 [QSP] (23 June 2010)
- D.1.22 Changes in MySQL 5.1.46 (06 April 2010)
- D.1.23 Changes in MySQL 5.1.45 (01 March 2010)
- D.1.24 Changes in MySQL 5.1.44 (04 February 2010)
- D.1.25 Changes in MySQL Enterprise 5.1.43sp1 [QSP] (25 March 2010)
- D.1.26 Changes in MySQL 5.1.43 (15 January 2010)
- D.1.27 Changes in MySQL 5.1.42 (15 December 2009)
- D.1.28 Changes in MySQL 5.1.41 (05 November 2009)
- D.1.29 Changes in MySQL Enterprise 5.1.40sp1 [QSP] (25 November 2009)
- D.1.30 Changes in MySQL 5.1.40 (06 October 2009)
- D.1.31 Changes in MySQL 5.1.39 (04 September 2009)
- D.1.32 Changes in MySQL 5.1.38 (01 September 2009)
- D.1.33 Changes in MySQL Enterprise 5.1.37sp1 [QSP] (10 October 2009)
- D.1.34 Changes in MySQL 5.1.37 (13 July 2009)
- D.1.35 Changes in MySQL 5.1.36 (16 June 2009)
- D.1.36 Changes in MySQL 5.1.35 (13 May 2009)
- D.1.37 Changes in MySQL Enterprise 5.1.34sp1 [QSP] (25 June 2009)
- D.1.38 Changes in MySQL 5.1.34 (02 April 2009)
- D.1.39 Changes in MySQL 5.1.33 (13 March 2009)
- D.1.40 Changes in MySQL 5.1.32 (14 February 2009)
- D.1.41 Changes in MySQL Enterprise 5.1.31sp1 [QSP] (19 March 2009)
- D.1.42 Changes in MySQL 5.1.31 (19 January 2009)
- D.1.43 Changes in MySQL 5.1.30 (14 November 2008, General Availability)
- D.1.44 Changes in MySQL 5.1.29 (11 October 2008)
- D.1.45 Changes in MySQL 5.1.28 (28 August 2008)
- D.1.46 Changes in MySQL 5.1.27 (Not released)
- D.1.47 Changes in MySQL 5.1.26 (30 June 2008)
- D.1.48 Changes in MySQL 5.1.25 (28 May 2008)
- D.1.49 Changes in MySQL 5.1.24 (08 April 2008)
- D.1.50 Changes in MySQL 5.1.23 (29 January 2008)
- D.1.51 Changes in MySQL 5.1.22 (24 September 2007, Release Candidate)
- D.1.52 Changes in MySQL 5.1.21 (16 August 2007)
- D.1.53 Changes in MySQL 5.1.20 (25 June 2007)
- D.1.54 Changes in MySQL 5.1.19 (25 May 2007)
- D.1.55 Changes in MySQL 5.1.18 (08 May 2007)
- D.1.56 Changes in MySQL 5.1.17 (04 April 2007)
- D.1.57 Changes in MySQL 5.1.16 (26 February 2007)
- D.1.58 Changes in MySQL 5.1.15 (25 January 2007)
- D.1.59 Changes in MySQL 5.1.14 (05 December 2006)
- D.1.60 Changes in MySQL 5.1.13 (Not released)
- D.1.61 Changes in MySQL 5.1.12 (24 October 2006)
- D.1.62 Changes in MySQL 5.1.11 (26 May 2006)
- D.1.63 Changes in MySQL 5.1.10 (Not released)
- D.1.64 Changes in MySQL 5.1.9 (12 April 2006)
- D.1.65 Changes in MySQL 5.1.8 (Not released)
- D.1.66 Changes in MySQL 5.1.7 (27 February 2006)
- D.1.67 Changes in MySQL 5.1.6 (01 February 2006)
- D.1.68 Changes in MySQL 5.1.5 (10 January 2006)
- D.1.69 Changes in MySQL 5.1.4 (21 December 2005)
- D.1.70 Changes in MySQL 5.1.3 (29 November 2005)
- D.1.71 Changes in MySQL 5.1.2 (Not released)
- D.1.72 Changes in MySQL 5.1.1 (Not released)
Bugs Fixed
-
Important Change: InnoDB: If an
ALTER TABLEstatement failed for anInnoDBtable due to an error code from an underlying file-renaming system call,InnoDBcould lose track of the.ibdfile for the table. This issue only occurred when theinnodb_file_per_tableconfiguration option was enabled, and when the low-level error persisted through thousands of retry attempts. In MySQL 5.1, this issue applied to the InnoDB Plugin but not the built-in InnoDB storage engine.For example, if you encounter an error like the following:
mysql> alter table sb2 add column d2 int; ERROR 1025 (HY000): Error on rename of './sbtest/#sql-1eb9_1' to './sbtest/sb2' (errno: -1)
you might be able to access the
#sql*table by copying a.frmfile from a table with an identical schema. The table name to use for the.frmfilewould be`sbtest.#mysql50##sql-1eb9_1`in the preceding example. (Bug #12884631, Bug #62146) InnoDB: Issuing
INSERT...ON DUPLICATE KEYstatements forInnoDBtables from concurrent threads could cause a deadlock, particularly with theINSERT...ON DUPLICATE KEY UPDATEform. The problem could also be triggered by issuing multipleINSERT IGNOREstatements. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. (Bug #11759688, Bug #52020, Bug #12842206)An incorrect
InnoDBassertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source filebtr0pcur.icand the variablecursor->pos_state. (Bug #13358468)The
handle_segfault()signal-handler code in mysqld could itself crash due to calling unsafe functions. (Bug #54082, Bug #11761576)ARCHIVEtables withNULLcolumns could cause server crashes or become corrupt under concurrent load. (Bug #51252, Bug #11758979)Enabling
myisam_use_mmapcould cause the server to crash. (Bug #48726, Bug #11756764)Concurrent access to
ARCHIVEtables could cause corruption. (Bug #42784, Bug #11751793)
User Comments
Add your own comment.