Merge lp:~hrvojem/percona-server/rn-5.5.29-30.0-fix into lp:percona-server/5.5

Proposed by Hrvoje Matijakovic on 2013-02-26
Status: Merged
Approved by: Laurynas Biveinis on 2013-02-26
Approved revision: 415
Merged at revision: 454
Proposed branch: lp:~hrvojem/percona-server/rn-5.5.29-30.0-fix
Merge into: lp:percona-server/5.5
Diff against target: 417 lines (+254/-18)
7 files modified
doc/source/conf.py (+1/-1)
doc/source/index.rst (+1/-0)
doc/source/management/changed_page_tracking.rst (+12/-2)
doc/source/performance/threadpool.rst (+113/-0)
doc/source/release-notes/Percona-Server-5.5.29-30.0.rst (+65/-0)
doc/source/release-notes/release-notes_index.rst (+25/-2)
doc/source/upstream-bug-fixes.rst (+37/-13)
To merge this branch: bzr merge lp:~hrvojem/percona-server/rn-5.5.29-30.0-fix
Reviewer Review Type Date Requested Status
Laurynas Biveinis (community) 2013-02-26 Approve on 2013-02-26
Review via email: mp+150492@code.launchpad.net
To post a comment you must log in.
415. By Hrvoje Matijakovic on 2013-02-26

 * release notes update

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== modified file 'doc/source/conf.py'
--- doc/source/conf.py 2013-01-18 11:03:40 +0000
+++ doc/source/conf.py 2013-02-26 06:06:40 +0000
@@ -54,7 +54,7 @@
54# The short X.Y version.54# The short X.Y version.
55version = '5.5'55version = '5.5'
56# The full version, including alpha/beta/rc tags.56# The full version, including alpha/beta/rc tags.
57release = '5.5.29-29.4'57release = '5.5.29-30.0'
5858
59# The language for content autogenerated by Sphinx. Refer to documentation59# The language for content autogenerated by Sphinx. Refer to documentation
60# for a list of supported languages.60# for a list of supported languages.
6161
=== modified file 'doc/source/index.rst'
--- doc/source/index.rst 2013-02-07 19:04:26 +0000
+++ doc/source/index.rst 2013-02-26 06:06:40 +0000
@@ -77,6 +77,7 @@
77 performance/innodb_thread_concurrency_timer_based77 performance/innodb_thread_concurrency_timer_based
78 performance/innodb_numa_support78 performance/innodb_numa_support
79 performance/handlersocket79 performance/handlersocket
80 performance/threadpool
8081
81Flexibility Improvements82Flexibility Improvements
82========================83========================
8384
=== modified file 'doc/source/management/changed_page_tracking.rst'
--- doc/source/management/changed_page_tracking.rst 2013-01-09 14:03:13 +0000
+++ doc/source/management/changed_page_tracking.rst 2013-02-26 06:06:40 +0000
@@ -15,6 +15,15 @@
1515
16This feature will be used for implementing faster incremental backups that use this information to avoid full data scans in |Percona XtraBackup|.16This feature will be used for implementing faster incremental backups that use this information to avoid full data scans in |Percona XtraBackup|.
1717
18User statements for handling the XtraDB changed page bitmaps
19============================================================
20
21In |Percona Server| :rn:`5.5.29-30.0` new statements have been introduced for handling the changed page bitmap tracking. All of these statements require ``SUPER`` privilege.
22
23 * ``FLUSH CHANGED_PAGE_BITMAPS`` - this statement can be used for synchronous bitmap write for immediate catch-up with the log checkpoint. This is used by innobackupex to make sure that XtraBackup indeed has all the required data it needs.
24 * ``RESET CHANGED_PAGE_BITMAPS`` - this statement will delete all the bitmap log files and restart the bitmap log file sequence.
25 * ``PURGE CHANGED_PAGE_BITMAPS BEFORE <lsn>`` - this statement will delete all the change page bitmap files up to the specified log sequence number.
26
18Additional information in SHOW ENGINE INNODB STATUS27Additional information in SHOW ENGINE INNODB STATUS
19===================================================28===================================================
20When log tracking is enabled, the following additional fields are displayed in the LOG section of the ``SHOW ENGINE INNODB STATUS`` output:29When log tracking is enabled, the following additional fields are displayed in the LOG section of the ``SHOW ENGINE INNODB STATUS`` output:
@@ -41,9 +50,10 @@
41System Variables50System Variables
42================51================
4352
44.. variable:: innodb_changed_pages_limit53.. variable:: innodb_max_changed_pages
4554
46 :version 5.5.27-29.0: Variable introduced55 :version 5.5.27-29.0: Variable :variable:`innodb_changed_pages_limit` introduced
56 :version 5.5.29-30.0: Variable renamed to :variable:`innodb_max_changed_pages`
47 :cli: Yes57 :cli: Yes
48 :conf: Yes58 :conf: Yes
49 :scope: Global59 :scope: Global
5060
=== added file 'doc/source/performance/threadpool.rst'
--- doc/source/performance/threadpool.rst 1970-01-01 00:00:00 +0000
+++ doc/source/performance/threadpool.rst 2013-02-26 06:06:40 +0000
@@ -0,0 +1,113 @@
1.. _threadpool:
2
3=============
4 Thread Pool
5=============
6
7.. note::
8
9 This feature implementation is considered BETA quality.
10
11|MySQL| executes statements using one thread per client connection. Once the number of connections increases past a certain point performance will degrade.
12
13This feature enables the server to keep the top performance even with large number of client connections by introducing a dynamic thread pool. By using the thread pool server would decrease the number of threads, which will then reduce the context switching and hot locks contentions. Using the thread pool will have the most effect with ``OLTP`` workloads (relatively short CPU-bound queries).
14
15In order to enable the thread pool variable :variable:`thread_handling` should be set up to ``pool-of-threads`` value. This can be done by adding: ::
16
17 thread_handling=pool-of-threads
18
19to the |MySQL| configuration file :file:`my.cnf`.
20
21Although the default values for the thread pool should provide good performance, additional `tuning <https://kb.askmonty.org/en/threadpool-in-55/#optimizing-server-variables-on-unix>`_ can be performed with the dynamic system variables described below.
22
23.. note::
24
25 Current implementation of the thread pool is built in the server, unlike the upstream version which is implemented as a plugin. Another significant implementation difference is that this implementation doesn't try to minimize the number of concurrent transactions like the ``MySQL Enterprise Threadpool``. Because of these things this implementation isn't compatible with the upstream one.
26
27Version Specific Information
28============================
29
30 * :rn:`5.5.29-30.0`
31 ``Thread Pool`` feature implemented. This feature was ported from |MariaDB|.
32
33System Variables
34================
35
36.. variable:: thread_pool_idle_timeout
37
38 :cli: Yes
39 :conf: Yes
40 :scope: Global
41 :dyn: Yes
42 :vartype: Numeric
43 :default: 60 (seconds)
44
45This variable can be used to limit the time an idle thread should wait before exiting.
46
47.. variable:: thread_pool_max_threads
48
49 :cli: Yes
50 :conf: Yes
51 :scope: Global
52 :dyn: Yes
53 :vartype: Numeric
54 :default: 500
55
56This variable can be used to limit the maximum number of threads in the pool. Once this number is reached no new threads will be created.
57
58.. variable:: thread_pool_oversubscribe
59
60 :cli: Yes
61 :conf: Yes
62 :scope: Global
63 :dyn: Yes
64 :vartype: Numeric
65 :default: 3
66
67The higher the value of this parameter the more threads can be run at the same time, if the values is lower than ``3`` it could lead to more sleeps and wake-ups.
68
69.. variable:: thread_pool_size
70
71 :cli: Yes
72 :conf: Yes
73 :scope: Global
74 :dyn: Yes
75 :vartype: Numeric
76 :default: Number of processors
77
78This variable can be used to define the number of threads that can use the CPU at the same time.
79
80.. variable:: thread_pool_stall_limit
81
82 :cli: Yes
83 :conf: No
84 :scope: Global
85 :dyn: No
86 :vartype: Numeric
87 :default: 500 (ms)
88
89The number of milliseconds before a running thread is considered stalled. When this limit is reached thread pool will wake up or create another thread. This is being used to prevent a long-running query from monopolizing the pool.
90
91Status Variables
92=====================
93
94.. variable:: Threadpool_idle_threads
95
96 :cli: Yes
97 :vartype: Numeric
98
99This status variable shows the number of idle threads in the pool.
100
101.. variable:: Threadpool_threads
102
103 :cli: Yes
104 :vartype: Numeric
105
106This status variable shows the number of threads in the pool.
107
108Other Reading
109=============
110
111 * `Thread pool in MariaDB 5.5 <https://kb.askmonty.org/en/threadpool-in-55/>`_
112
113 * `Thread pool implementation in Oracle MySQL <http://mikaelronstrom.blogspot.com/2011_10_01_archive.html>`_
0114
=== added file 'doc/source/release-notes/Percona-Server-5.5.29-30.0.rst'
--- doc/source/release-notes/Percona-Server-5.5.29-30.0.rst 1970-01-01 00:00:00 +0000
+++ doc/source/release-notes/Percona-Server-5.5.29-30.0.rst 2013-02-26 06:06:40 +0000
@@ -0,0 +1,65 @@
1.. rn:: 5.5.29-30.0
2
3==============================
4 |Percona Server| 5.5.29-30.0
5==============================
6
7Percona is glad to announce the release of |Percona Server| 5.5.29-30.0 on February 26th, 2012 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.5/Percona-Server-5.5.29-30.0/>`_ and from the `Percona Software Repositories <http://www.percona.com/docs/wiki/repositories:start>`_).
8
9Based on `MySQL 5.5.29 <http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-29.html>`_, including all the bug fixes in it, |Percona Server| 5.5.29-30.0 is now the current stable release in the 5.5 series. All of |Percona|'s software is open-source and free, all the details of the release can be found in the `5.5.29-30.0 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.5.29-30.0>`_.
10
11New Features
12============
13
14 Ported the :ref:`threadpool` patch from |MariaDB|. This feature enables the server to keep the top performance even with the increased number of client connections.
15
16 New user statements have been introduced for handling the :ref:`changed_page_tracking` log files.
17
18 In addition to the :option:`--debug` build option for :file:`build-binary.sh` script, new :option:`--valgrind` option has been introduced, which will build debug builds with the `Valgrind <http://valgrind.org/>`_ instrumentation enabled.
19
20Bug Fixes
21=========
22
23 Ported a fix from `MariaDB <https://mariadb.atlassian.net/browse/MDEV-364>`_ for the upstream bug :mysqlbug:`67974`, which caused server crash on concurrent ``ALTER TABLE`` and ``SHOW ENGINE INNODB STATUS``. Bug fixed :bug:`1017192` (*Sergei Glushchenko*).
24
25 The server could crash when executing an ``INSERT`` or ``UPDATE`` statement containing ``BLOB`` values for a compressed table. This regression was introduced in |Percona Server| :rn:`5.5.28-29.2`. Bug fixed :bug:`1100159` (*Laurynas Biveinis*).
26
27 Upstream bug :mysqlbug:`67983` was causing a memory leak on a filtered slave. Bug fixed :bug:`1042946` (*Sergei Glushchenko*).
28
29 |Percona Server| would fail to install on a vanilla *Ubuntu* 12.04 server. Bug fixed :bug:`1103655` (*Ignacio Nin*).
30
31 The master thread was doing dirty buffer pool flush list reads to make its adaptive flushing decisions. Fixed by acquiring the flush list mutex around the list scans. Bug fixed :bug:`1083058` (*Laurynas Biveinis*).
32
33 Upstream changes made to improve |InnoDB| ``DROP TABLE`` performance were not adjusted for |XtraDB|. This could cause server assertion errors. Bugs fixed :bug:`934377`, bug :bug:`1111211`, bug :bug:`1116447` and :bug:`1110102` (*Laurynas Biveinis*).
34
35 The |XtraDB| used to print the open read view list without taking the kernel mutex. Thus any list element might become invalid during its iteration. Fixed by taking the kernel mutex. Bug fixed :bug:`1101030` (*Laurynas Biveinis*).
36
37 When option :variable:`innodb_flush_method=O_DIRECT` was set up, log bitmap files were created and treated as |InnoDB| data files for flushing purposes, which wasn't original intention. Bug fixed :bug:`1105709` (*Laurynas Biveinis*).
38
39 ``INFORMATION_SCHEMA`` plugin name :variable:`innodb_changed_pages` serves also as a command line option, but it is also a prefix of another command line option :variable:`innodb_changed_pages_limit`. |MySQL| option handling would then shadow the former with the latter, resulting in start up errors. Fixed by renaming the :variable:`innodb_changed_pages_limit` option to :variable:`innodb_max_changed_pages`. Bug fixed :bug:`1105726` (*Laurynas Biveinis*).
40
41 Time in slow query log was displayed incorrectly when :variable:`slow_query_log_timestamp_precision` variable was set to microseconds. Bug fixed :bug:`887928` (*Laurynas Biveinis*).
42
43 Writing bitmap larger than 4GB would cause write to fail. Also a write error for every bitmap page, except the first one, would result in a heap corruption. Bug fixed :bug:`1111226` (*Laurynas Biveinis*).
44
45 Fixed the upstream bug :mysqlbug:`67504` that caused spurious duplicate key errors. Errors would happen if a trigger is fired while a slave was processing replication events for a table that is present only on slave server while there are updates on the replicated table on the master which is used in that trigger. For this to happen master needs to have more than one auto-increment table and the slave needs to have at least one of those tables specified in the :variable:`replicate-ignore-table`. Bug fixed :bug:`1068210` (*George Ormond Lorch III*).
46
47 Fixed failing ``rpm`` builds, that were caused by missing files. Bug fixed :bug:`1099809` (*Alexey Bychko*).
48
49 Fixed the upstream :mysqlbug:`68116` that caused the server crash with assertion error when |InnoDB| monitor with verbose lock info was used under heavy load. This bug is affecting only ``-debug`` builds. Bug fixed :bug:`1100178` (*Laurynas Biveinis*).
50
51 :ref:`changed_page_tracking` wasn't compatible with :option:`innodb_force_recovery=6`. When starting the server log tracking initialization would fail. The server would abort on startup. Bug fixed :bug:`1083596` (*Laurynas Biveinis*).
52
53 Newly created bitmap file would silently overwrite the old one if they had the same file name. Bug fixed :bug:`1111144` (*Laurynas Biveinis*).
54
55 A server would stop with an assertion error in I/O and AIO routines if large :variable:`innodb_log_block_size` value is used in the combination with changed page tracking. Bug fixed :bug:`1114612` (*Laurynas Biveinis*).
56
57 ``Optimizer_fix`` patch has been removed from |Percona Server|. Bug fixed :bug:`986247` (*Stewart Smith*).
58
59 |InnoDB| monitor was prefetching the data pages for printing lock information even if no lock information was going to be printed. Bug fixed :bug:`1100643` (*Laurynas Biveinis*).
60
61 |InnoDB| and the query plan information were being logged even if they weren't enabled for the slow query log. Bug fixed :bug:`730173` (*Laurynas Biveinis*).
62
63 Fixed the incorrect help text for :variable:`slow_query_log_timestamp_precision`. Bug fixed :bug:`1090965` (*Laurynas Biveinis*).
64
65Other bug fixes: bug fixed :bug:`909376` (*Laurynas Biveinis*), bug fixed :bug:`1082437` (*Laurynas Biveinis*), bug fixed :bug:`1083669` (*Laurynas Biveinis*), bug fixed :bug:`1096904` (*Laurynas Biveinis*), bug fixed :bug:`1091712` (*Laurynas Biveinis*), bug fixed :bug:`1096899` (*Laurynas Biveinis*), bug fixed :bug:`1088954` (*Laurynas Biveinis*), bug fixed :bug:`1096895` (*Laurynas Biveinis*), bug fixed :bug:`1092142` (*Laurynas Biveinis*), bug fixed :bug:`1090874` (*Laurynas Biveinis*), bug fixed :bug:`1089961` (*Laurynas Biveinis*), bug fixed :bug:`1088867` (*Laurynas Biveinis*), bug fixed :bug:`1089031` (*Laurynas Biveinis*), bug fixed :bug:`1108874` (*Laurynas Biveinis*).
066
=== modified file 'doc/source/release-notes/release-notes_index.rst'
--- doc/source/release-notes/release-notes_index.rst 2012-09-18 05:04:43 +0000
+++ doc/source/release-notes/release-notes_index.rst 2013-02-26 06:06:40 +0000
@@ -6,6 +6,29 @@
6 :maxdepth: 16 :maxdepth: 1
7 :glob:7 :glob:
88
9 Percona-Server-5.5.29-30.0
10 Percona-Server-5.5.29-29.4
11 Percona-Server-5.5.28-29.3
12 Percona-Server-5.5.28-29.2
13 Percona-Server-5.5.28-29.1
14 Percona-Server-5.5.27-29.0
15 Percona-Server-5.5.27-28.1
16 Percona-Server-5.5.27-28.0
17 Percona-Server-5.5.25a-27.1
18 Percona-Server-5.5.24-26.0
19 Percona-Server-5.5.23-25.3
20 Percona-Server-5.5.22-25.2
21 Percona-Server-5.5.21-25.1
22 Percona-Server-5.5.21-25.0
23 Percona-Server-5.5.20-24.1
24 Percona-Server-5.5.19-24.0
25 Percona-Server-5.5.18-23.0
26 Percona-Server-5.5.17-22.1
27 Percona-Server-5.5.16-22.0
28 Percona-Server-5.5.15-21.0
29 Percona-Server-5.5.14-20.5
30 Percona-Server-5.5.13-20.4
31 Percona-Server-5.5.12-20.3
32 Percona-Server-5.5.11-20.2
33 Percona-Server-5.5.10-20.1
9 Percona-Server-5.5.8-20.034 Percona-Server-5.5.8-20.0
10 Percona-Server-5.5.1*
11 Percona-Server-5.5.2*
1235
=== modified file 'doc/source/upstream-bug-fixes.rst'
--- doc/source/upstream-bug-fixes.rst 2013-01-18 11:03:40 +0000
+++ doc/source/upstream-bug-fixes.rst 2013-02-26 06:06:40 +0000
@@ -5,6 +5,30 @@
5=============================================================5=============================================================
66
7+-------------------------------------------------------------------------------------------------------------+7+-------------------------------------------------------------------------------------------------------------+
8|:Upstream bug: :mysqlbug:`68116` - InnoDB monitor may hit an assertion error in buf_page_get_gen in debug ...|
9|:Launchpad bug: :bug:`1100178` |
10|:Upstream state: Analyzing (checked on 2013-02-21) |
11|:Fix Released: :rn:`5.5.29-30.0` |
12|:Upstream fix: N/A |
13+-------------------------------------------------------------------------------------------------------------+
14|:Upstream bug: :mysqlbug:`67504` - Duplicate error in replication with slave triggers and auto increment |
15|:Launchpad bug: :bug:`1068210` |
16|:Upstream state: Verified (checked on 2013-02-21) |
17|:Fix Released: :rn:`5.5.29-30.0` |
18|:Upstream fix: N/A |
19+-------------------------------------------------------------------------------------------------------------+
20|:Upstream bug: :mysqlbug:`67983` - Memory leak on filtered slave |
21|:Launchpad bug: :bug:`1042946` |
22|:Upstream state: Closed |
23|:Fix Released: :rn:`5.5.29-30.0` |
24|:Upstream fix: 5.5.31 |
25+-------------------------------------------------------------------------------------------------------------+
26|:Upstream bug: :mysqlbug:`67974` - Server crashes in add_identifier on concurrent ALTER TABLE and SHOW ENGINE|
27|:Launchpad bug: :bug:`1017192` |
28|:Upstream state: N/A |
29|:Fix Released: :rn:`5.5.29-30.0` |
30|:Upstream fix: N/A |
31+-------------------------------------------------------------------------------------------------------------+
8|:Upstream bug: :mysqlbug:`68045` - security vulnerability CVE-2012-4414 |32|:Upstream bug: :mysqlbug:`68045` - security vulnerability CVE-2012-4414 |
9|:Launchpad bug: :bug:`1049871` |33|:Launchpad bug: :bug:`1049871` |
10|:Upstream state: N/A |34|:Upstream state: N/A |
@@ -25,7 +49,7 @@
25+-------------------------------------------------------------------------------------------------------------+49+-------------------------------------------------------------------------------------------------------------+
26|:Upstream bug: :mysqlbug:`66237` - Temporary files created by binary log cache are not purged after transa...|50|:Upstream bug: :mysqlbug:`66237` - Temporary files created by binary log cache are not purged after transa...|
27|:Launchpad bug: :bug:`1070856` |51|:Launchpad bug: :bug:`1070856` |
28|:Upstream state: Verified (checked on 2013-01-18) |52|:Upstream state: Verified (checked on 2013-02-21) |
29|:Fix Released: :rn:`5.5.28-29.3` |53|:Fix Released: :rn:`5.5.28-29.3` |
30|:Upstream fix: N/A |54|:Upstream fix: N/A |
31+-------------------------------------------------------------------------------------------------------------+55+-------------------------------------------------------------------------------------------------------------+
@@ -43,55 +67,55 @@
43+-------------------------------------------------------------------------------------------------------------+67+-------------------------------------------------------------------------------------------------------------+
44|:Upstream bug: :mysqlbug:`62856` - Check for "stack overrun" doesn't work with gcc-4.6, server crashes |68|:Upstream bug: :mysqlbug:`62856` - Check for "stack overrun" doesn't work with gcc-4.6, server crashes |
45|:Launchpad bug: :bug:`1042517` |69|:Launchpad bug: :bug:`1042517` |
46|:Upstream state: Verified (checked on 2013-01-18) |70|:Upstream state: Verified (checked on 2013-02-21) |
47|:Fix Released: :rn:`5.5.28-29.1` |71|:Fix Released: :rn:`5.5.28-29.1` |
48|:Upstream fix: N/A |72|:Upstream fix: N/A |
49+-------------------------------------------------------------------------------------------------------------+73+-------------------------------------------------------------------------------------------------------------+
50|:Upstream bug: :mysqlbug:`61180` - korr/store macros in my_global.h assume the argument to be a char pointer |74|:Upstream bug: :mysqlbug:`61180` - korr/store macros in my_global.h assume the argument to be a char pointer |
51|:Launchpad bug: :bug:`1042517` |75|:Launchpad bug: :bug:`1042517` |
52|:Upstream state: Verified (checked on 2013-01-18) |76|:Upstream state: Verified (checked on 2013-02-21) |
53|:Fix Released: :rn:`5.5.27-29.0` |77|:Fix Released: :rn:`5.5.27-29.0` |
54|:Upstream fix: N/A |78|:Upstream fix: N/A |
55+-------------------------------------------------------------------------------------------------------------+79+-------------------------------------------------------------------------------------------------------------+
56|:Upstream bug: :mysqlbug:`61179` - Unoptimized versions of korr/store macros in my_global.h are used on ... |80|:Upstream bug: :mysqlbug:`61179` - Unoptimized versions of korr/store macros in my_global.h are used on ... |
57|:Launchpad bug: :bug:`1042517` |81|:Launchpad bug: :bug:`1042517` |
58|:Upstream state: Verified (checked on 2013-01-18) |82|:Upstream state: Verified (checked on 2013-02-21) |
59|:Fix Released: :rn:`5.5.27-29.0` |83|:Fix Released: :rn:`5.5.27-29.0` |
60|:Upstream fix: N/A |84|:Upstream fix: N/A |
61+-------------------------------------------------------------------------------------------------------------+85+-------------------------------------------------------------------------------------------------------------+
62|:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|86|:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|
63|:Launchpad bug: :bug:`1042517` |87|:Launchpad bug: :bug:`1042517` |
64|:Upstream state: Verified (checked on 2013-01-18) |88|:Upstream state: Verified (checked on 2013-02-21) |
65|:Fix Released: :rn:`5.5.27-29.0` |89|:Fix Released: :rn:`5.5.27-29.0` |
66|:Upstream fix: N/A |90|:Upstream fix: N/A |
67+-------------------------------------------------------------------------------------------------------------+91+-------------------------------------------------------------------------------------------------------------+
68|:Upstream bug: :mysqlbug:`54127` - mysqld segfaults when built using --with-max-indexes=128 |92|:Upstream bug: :mysqlbug:`54127` - mysqld segfaults when built using --with-max-indexes=128 |
69|:Launchpad bug: :bug:`1042517` |93|:Launchpad bug: :bug:`1042517` |
70|:Upstream state: Verified (checked on 2013-01-18) |94|:Upstream state: Verified (checked on 2013-02-21) |
71|:Fix Released: :rn:`5.5.27-29.0` |95|:Fix Released: :rn:`5.5.27-29.0` |
72|:Upstream fix: N/A |96|:Upstream fix: N/A |
73+-------------------------------------------------------------------------------------------------------------+97+-------------------------------------------------------------------------------------------------------------+
74|:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no. | 98|:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no. |
75|:Launchpad bug: :bug:`1013432` |99|:Launchpad bug: :bug:`1013432` |
76|:Upstream state: Verified (checked on 2013-01-18) |100|:Upstream state: Verified (checked on 2013-02-21) |
77|:Fix Released: :rn:`5.5.27-28.0` |101|:Fix Released: :rn:`5.5.27-28.0` |
78|:Upstream fix: N/A |102|:Upstream fix: N/A |
79+-------------------------------------------------------------------------------------------------------------+103+-------------------------------------------------------------------------------------------------------------+
80|:Upstream bug: :mysqlbug:`66301` - INSERT ... ON DUPLICATE KEY UPDATE + innodb_autoinc_lock_mode=1 is broken |104|:Upstream bug: :mysqlbug:`66301` - INSERT ... ON DUPLICATE KEY UPDATE + innodb_autoinc_lock_mode=1 is broken |
81|:Launchpad bug: :bug:`1035225` |105|:Launchpad bug: :bug:`1035225` |
82|:Upstream state: Verified (checked on 2013-01-18) |106|:Upstream state: Verified (checked on 2013-02-21) |
83|:Fix Released: :rn:`5.5.27-28.0` |107|:Fix Released: :rn:`5.5.27-28.0` |
84|:Upstream fix: N/A |108|:Upstream fix: N/A |
85+-------------------------------------------------------------------------------------------------------------+109+-------------------------------------------------------------------------------------------------------------+
86|:Upstream bug: :mysqlbug:`60743` - typo in cmake/dtrace.cmake |110|:Upstream bug: :mysqlbug:`60743` - typo in cmake/dtrace.cmake |
87|:Launchpad bug: :bug:`1013455` |111|:Launchpad bug: :bug:`1013455` |
88|:Upstream state: Verified (checked on 2013-01-18) |112|:Upstream state: Verified (checked on 2013-02-21) |
89|:Fix Released: :rn:`5.5.25a-27.1` |113|:Fix Released: :rn:`5.5.25a-27.1` |
90|:Upstream fix: N/A |114|:Upstream fix: N/A |
91+-------------------------------------------------------------------------------------------------------------+115+-------------------------------------------------------------------------------------------------------------+
92|:Upstream bug: :mysqlbug:`64663` - Segfault when adding indexes to InnoDB temporary tables |116|:Upstream bug: :mysqlbug:`64663` - Segfault when adding indexes to InnoDB temporary tables |
93|:Launchpad bug: :bug:`999147` |117|:Launchpad bug: :bug:`999147` |
94|:Upstream state: Verified (checked on 2013-01-18) |118|:Upstream state: Verified (checked on 2013-02-21) |
95|:Fix Released: :rn:`5.5.24-26.0` |119|:Fix Released: :rn:`5.5.24-26.0` |
96|:Upstream fix: N/A |120|:Upstream fix: N/A |
97+-------------------------------------------------------------------------------------------------------------+121+-------------------------------------------------------------------------------------------------------------+
@@ -109,7 +133,7 @@
109+-------------------------------------------------------------------------------------------------------------+133+-------------------------------------------------------------------------------------------------------------+
110|:Upstream bug: :mysqlbug:`64432` - Bug :mysqlbug:`54330` (Broken fast index creation) was never fixed in 5.5 |134|:Upstream bug: :mysqlbug:`64432` - Bug :mysqlbug:`54330` (Broken fast index creation) was never fixed in 5.5 |
111|:Launchpad bug: :bug:`939485` |135|:Launchpad bug: :bug:`939485` |
112|:Upstream state: Documenting (checked on 2013-01-18) |136|:Upstream state: Documenting (checked on 2013-02-21) |
113|:Fix Released: :rn:`5.5.21-25.0` |137|:Fix Released: :rn:`5.5.21-25.0` |
114|:Upstream fix: N/A |138|:Upstream fix: N/A |
115+-------------------------------------------------------------------------------------------------------------+139+-------------------------------------------------------------------------------------------------------------+
@@ -133,7 +157,7 @@
133+-------------------------------------------------------------------------------------------------------------+157+-------------------------------------------------------------------------------------------------------------+
134|:Upstream bug: :mysqlbug:`62516` - Fast index creation does not update index statistics |158|:Upstream bug: :mysqlbug:`62516` - Fast index creation does not update index statistics |
135|:Launchpad bug: :bug:`857590` |159|:Launchpad bug: :bug:`857590` |
136|:Upstream state: Verified (checked on 2013-01-18) |160|:Upstream state: Verified (checked on 2013-02-21) |
137|:Fix Released: :rn:`5.5.16-22.0` |161|:Fix Released: :rn:`5.5.16-22.0` |
138|:Upstream fix: N/A |162|:Upstream fix: N/A |
139+-------------------------------------------------------------------------------------------------------------+163+-------------------------------------------------------------------------------------------------------------+
@@ -145,7 +169,7 @@
145+-------------------------------------------------------------------------------------------------------------+169+-------------------------------------------------------------------------------------------------------------+
146|:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |170|:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |
147|:Launchpad bug: :bug:`800035` |171|:Launchpad bug: :bug:`800035` |
148|:Upstream state: Verified (checked on 2013-01-18) |172|:Upstream state: Verified (checked on 2013-02-21) |
149|:Fix Released: :rn:`5.5.13-20.4` |173|:Fix Released: :rn:`5.5.13-20.4` |
150|:Upstream fix: N/A |174|:Upstream fix: N/A |
151+-------------------------------------------------------------------------------------------------------------+175+-------------------------------------------------------------------------------------------------------------+

Subscribers

People subscribed via source and target branches