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
1=== modified file 'doc/source/conf.py'
2--- doc/source/conf.py 2013-01-18 11:03:40 +0000
3+++ doc/source/conf.py 2013-02-26 06:06:40 +0000
4@@ -54,7 +54,7 @@
5 # The short X.Y version.
6 version = '5.5'
7 # The full version, including alpha/beta/rc tags.
8-release = '5.5.29-29.4'
9+release = '5.5.29-30.0'
10
11 # The language for content autogenerated by Sphinx. Refer to documentation
12 # for a list of supported languages.
13
14=== modified file 'doc/source/index.rst'
15--- doc/source/index.rst 2013-02-07 19:04:26 +0000
16+++ doc/source/index.rst 2013-02-26 06:06:40 +0000
17@@ -77,6 +77,7 @@
18 performance/innodb_thread_concurrency_timer_based
19 performance/innodb_numa_support
20 performance/handlersocket
21+ performance/threadpool
22
23 Flexibility Improvements
24 ========================
25
26=== modified file 'doc/source/management/changed_page_tracking.rst'
27--- doc/source/management/changed_page_tracking.rst 2013-01-09 14:03:13 +0000
28+++ doc/source/management/changed_page_tracking.rst 2013-02-26 06:06:40 +0000
29@@ -15,6 +15,15 @@
30
31 This feature will be used for implementing faster incremental backups that use this information to avoid full data scans in |Percona XtraBackup|.
32
33+User statements for handling the XtraDB changed page bitmaps
34+============================================================
35+
36+In |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.
37+
38+ * ``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.
39+ * ``RESET CHANGED_PAGE_BITMAPS`` - this statement will delete all the bitmap log files and restart the bitmap log file sequence.
40+ * ``PURGE CHANGED_PAGE_BITMAPS BEFORE <lsn>`` - this statement will delete all the change page bitmap files up to the specified log sequence number.
41+
42 Additional information in SHOW ENGINE INNODB STATUS
43 ===================================================
44 When log tracking is enabled, the following additional fields are displayed in the LOG section of the ``SHOW ENGINE INNODB STATUS`` output:
45@@ -41,9 +50,10 @@
46 System Variables
47 ================
48
49-.. variable:: innodb_changed_pages_limit
50+.. variable:: innodb_max_changed_pages
51
52- :version 5.5.27-29.0: Variable introduced
53+ :version 5.5.27-29.0: Variable :variable:`innodb_changed_pages_limit` introduced
54+ :version 5.5.29-30.0: Variable renamed to :variable:`innodb_max_changed_pages`
55 :cli: Yes
56 :conf: Yes
57 :scope: Global
58
59=== added file 'doc/source/performance/threadpool.rst'
60--- doc/source/performance/threadpool.rst 1970-01-01 00:00:00 +0000
61+++ doc/source/performance/threadpool.rst 2013-02-26 06:06:40 +0000
62@@ -0,0 +1,113 @@
63+.. _threadpool:
64+
65+=============
66+ Thread Pool
67+=============
68+
69+.. note::
70+
71+ This feature implementation is considered BETA quality.
72+
73+|MySQL| executes statements using one thread per client connection. Once the number of connections increases past a certain point performance will degrade.
74+
75+This 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).
76+
77+In 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: ::
78+
79+ thread_handling=pool-of-threads
80+
81+to the |MySQL| configuration file :file:`my.cnf`.
82+
83+Although 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.
84+
85+.. note::
86+
87+ 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.
88+
89+Version Specific Information
90+============================
91+
92+ * :rn:`5.5.29-30.0`
93+ ``Thread Pool`` feature implemented. This feature was ported from |MariaDB|.
94+
95+System Variables
96+================
97+
98+.. variable:: thread_pool_idle_timeout
99+
100+ :cli: Yes
101+ :conf: Yes
102+ :scope: Global
103+ :dyn: Yes
104+ :vartype: Numeric
105+ :default: 60 (seconds)
106+
107+This variable can be used to limit the time an idle thread should wait before exiting.
108+
109+.. variable:: thread_pool_max_threads
110+
111+ :cli: Yes
112+ :conf: Yes
113+ :scope: Global
114+ :dyn: Yes
115+ :vartype: Numeric
116+ :default: 500
117+
118+This 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.
119+
120+.. variable:: thread_pool_oversubscribe
121+
122+ :cli: Yes
123+ :conf: Yes
124+ :scope: Global
125+ :dyn: Yes
126+ :vartype: Numeric
127+ :default: 3
128+
129+The 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.
130+
131+.. variable:: thread_pool_size
132+
133+ :cli: Yes
134+ :conf: Yes
135+ :scope: Global
136+ :dyn: Yes
137+ :vartype: Numeric
138+ :default: Number of processors
139+
140+This variable can be used to define the number of threads that can use the CPU at the same time.
141+
142+.. variable:: thread_pool_stall_limit
143+
144+ :cli: Yes
145+ :conf: No
146+ :scope: Global
147+ :dyn: No
148+ :vartype: Numeric
149+ :default: 500 (ms)
150+
151+The 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.
152+
153+Status Variables
154+=====================
155+
156+.. variable:: Threadpool_idle_threads
157+
158+ :cli: Yes
159+ :vartype: Numeric
160+
161+This status variable shows the number of idle threads in the pool.
162+
163+.. variable:: Threadpool_threads
164+
165+ :cli: Yes
166+ :vartype: Numeric
167+
168+This status variable shows the number of threads in the pool.
169+
170+Other Reading
171+=============
172+
173+ * `Thread pool in MariaDB 5.5 <https://kb.askmonty.org/en/threadpool-in-55/>`_
174+
175+ * `Thread pool implementation in Oracle MySQL <http://mikaelronstrom.blogspot.com/2011_10_01_archive.html>`_
176
177=== added file 'doc/source/release-notes/Percona-Server-5.5.29-30.0.rst'
178--- doc/source/release-notes/Percona-Server-5.5.29-30.0.rst 1970-01-01 00:00:00 +0000
179+++ doc/source/release-notes/Percona-Server-5.5.29-30.0.rst 2013-02-26 06:06:40 +0000
180@@ -0,0 +1,65 @@
181+.. rn:: 5.5.29-30.0
182+
183+==============================
184+ |Percona Server| 5.5.29-30.0
185+==============================
186+
187+Percona 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>`_).
188+
189+Based 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>`_.
190+
191+New Features
192+============
193+
194+ 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.
195+
196+ New user statements have been introduced for handling the :ref:`changed_page_tracking` log files.
197+
198+ 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.
199+
200+Bug Fixes
201+=========
202+
203+ 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*).
204+
205+ 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*).
206+
207+ Upstream bug :mysqlbug:`67983` was causing a memory leak on a filtered slave. Bug fixed :bug:`1042946` (*Sergei Glushchenko*).
208+
209+ |Percona Server| would fail to install on a vanilla *Ubuntu* 12.04 server. Bug fixed :bug:`1103655` (*Ignacio Nin*).
210+
211+ 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*).
212+
213+ 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*).
214+
215+ 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*).
216+
217+ 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*).
218+
219+ ``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*).
220+
221+ 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*).
222+
223+ 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*).
224+
225+ 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*).
226+
227+ Fixed failing ``rpm`` builds, that were caused by missing files. Bug fixed :bug:`1099809` (*Alexey Bychko*).
228+
229+ 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*).
230+
231+ :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*).
232+
233+ Newly created bitmap file would silently overwrite the old one if they had the same file name. Bug fixed :bug:`1111144` (*Laurynas Biveinis*).
234+
235+ 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*).
236+
237+ ``Optimizer_fix`` patch has been removed from |Percona Server|. Bug fixed :bug:`986247` (*Stewart Smith*).
238+
239+ |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*).
240+
241+ |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*).
242+
243+ Fixed the incorrect help text for :variable:`slow_query_log_timestamp_precision`. Bug fixed :bug:`1090965` (*Laurynas Biveinis*).
244+
245+Other 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*).
246
247=== modified file 'doc/source/release-notes/release-notes_index.rst'
248--- doc/source/release-notes/release-notes_index.rst 2012-09-18 05:04:43 +0000
249+++ doc/source/release-notes/release-notes_index.rst 2013-02-26 06:06:40 +0000
250@@ -6,6 +6,29 @@
251 :maxdepth: 1
252 :glob:
253
254+ Percona-Server-5.5.29-30.0
255+ Percona-Server-5.5.29-29.4
256+ Percona-Server-5.5.28-29.3
257+ Percona-Server-5.5.28-29.2
258+ Percona-Server-5.5.28-29.1
259+ Percona-Server-5.5.27-29.0
260+ Percona-Server-5.5.27-28.1
261+ Percona-Server-5.5.27-28.0
262+ Percona-Server-5.5.25a-27.1
263+ Percona-Server-5.5.24-26.0
264+ Percona-Server-5.5.23-25.3
265+ Percona-Server-5.5.22-25.2
266+ Percona-Server-5.5.21-25.1
267+ Percona-Server-5.5.21-25.0
268+ Percona-Server-5.5.20-24.1
269+ Percona-Server-5.5.19-24.0
270+ Percona-Server-5.5.18-23.0
271+ Percona-Server-5.5.17-22.1
272+ Percona-Server-5.5.16-22.0
273+ Percona-Server-5.5.15-21.0
274+ Percona-Server-5.5.14-20.5
275+ Percona-Server-5.5.13-20.4
276+ Percona-Server-5.5.12-20.3
277+ Percona-Server-5.5.11-20.2
278+ Percona-Server-5.5.10-20.1
279 Percona-Server-5.5.8-20.0
280- Percona-Server-5.5.1*
281- Percona-Server-5.5.2*
282
283=== modified file 'doc/source/upstream-bug-fixes.rst'
284--- doc/source/upstream-bug-fixes.rst 2013-01-18 11:03:40 +0000
285+++ doc/source/upstream-bug-fixes.rst 2013-02-26 06:06:40 +0000
286@@ -5,6 +5,30 @@
287 =============================================================
288
289 +-------------------------------------------------------------------------------------------------------------+
290+|:Upstream bug: :mysqlbug:`68116` - InnoDB monitor may hit an assertion error in buf_page_get_gen in debug ...|
291+|:Launchpad bug: :bug:`1100178` |
292+|:Upstream state: Analyzing (checked on 2013-02-21) |
293+|:Fix Released: :rn:`5.5.29-30.0` |
294+|:Upstream fix: N/A |
295++-------------------------------------------------------------------------------------------------------------+
296+|:Upstream bug: :mysqlbug:`67504` - Duplicate error in replication with slave triggers and auto increment |
297+|:Launchpad bug: :bug:`1068210` |
298+|:Upstream state: Verified (checked on 2013-02-21) |
299+|:Fix Released: :rn:`5.5.29-30.0` |
300+|:Upstream fix: N/A |
301++-------------------------------------------------------------------------------------------------------------+
302+|:Upstream bug: :mysqlbug:`67983` - Memory leak on filtered slave |
303+|:Launchpad bug: :bug:`1042946` |
304+|:Upstream state: Closed |
305+|:Fix Released: :rn:`5.5.29-30.0` |
306+|:Upstream fix: 5.5.31 |
307++-------------------------------------------------------------------------------------------------------------+
308+|:Upstream bug: :mysqlbug:`67974` - Server crashes in add_identifier on concurrent ALTER TABLE and SHOW ENGINE|
309+|:Launchpad bug: :bug:`1017192` |
310+|:Upstream state: N/A |
311+|:Fix Released: :rn:`5.5.29-30.0` |
312+|:Upstream fix: N/A |
313++-------------------------------------------------------------------------------------------------------------+
314 |:Upstream bug: :mysqlbug:`68045` - security vulnerability CVE-2012-4414 |
315 |:Launchpad bug: :bug:`1049871` |
316 |:Upstream state: N/A |
317@@ -25,7 +49,7 @@
318 +-------------------------------------------------------------------------------------------------------------+
319 |:Upstream bug: :mysqlbug:`66237` - Temporary files created by binary log cache are not purged after transa...|
320 |:Launchpad bug: :bug:`1070856` |
321-|:Upstream state: Verified (checked on 2013-01-18) |
322+|:Upstream state: Verified (checked on 2013-02-21) |
323 |:Fix Released: :rn:`5.5.28-29.3` |
324 |:Upstream fix: N/A |
325 +-------------------------------------------------------------------------------------------------------------+
326@@ -43,55 +67,55 @@
327 +-------------------------------------------------------------------------------------------------------------+
328 |:Upstream bug: :mysqlbug:`62856` - Check for "stack overrun" doesn't work with gcc-4.6, server crashes |
329 |:Launchpad bug: :bug:`1042517` |
330-|:Upstream state: Verified (checked on 2013-01-18) |
331+|:Upstream state: Verified (checked on 2013-02-21) |
332 |:Fix Released: :rn:`5.5.28-29.1` |
333 |:Upstream fix: N/A |
334 +-------------------------------------------------------------------------------------------------------------+
335 |:Upstream bug: :mysqlbug:`61180` - korr/store macros in my_global.h assume the argument to be a char pointer |
336 |:Launchpad bug: :bug:`1042517` |
337-|:Upstream state: Verified (checked on 2013-01-18) |
338+|:Upstream state: Verified (checked on 2013-02-21) |
339 |:Fix Released: :rn:`5.5.27-29.0` |
340 |:Upstream fix: N/A |
341 +-------------------------------------------------------------------------------------------------------------+
342 |:Upstream bug: :mysqlbug:`61179` - Unoptimized versions of korr/store macros in my_global.h are used on ... |
343 |:Launchpad bug: :bug:`1042517` |
344-|:Upstream state: Verified (checked on 2013-01-18) |
345+|:Upstream state: Verified (checked on 2013-02-21) |
346 |:Fix Released: :rn:`5.5.27-29.0` |
347 |:Upstream fix: N/A |
348 +-------------------------------------------------------------------------------------------------------------+
349 |:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|
350 |:Launchpad bug: :bug:`1042517` |
351-|:Upstream state: Verified (checked on 2013-01-18) |
352+|:Upstream state: Verified (checked on 2013-02-21) |
353 |:Fix Released: :rn:`5.5.27-29.0` |
354 |:Upstream fix: N/A |
355 +-------------------------------------------------------------------------------------------------------------+
356 |:Upstream bug: :mysqlbug:`54127` - mysqld segfaults when built using --with-max-indexes=128 |
357 |:Launchpad bug: :bug:`1042517` |
358-|:Upstream state: Verified (checked on 2013-01-18) |
359+|:Upstream state: Verified (checked on 2013-02-21) |
360 |:Fix Released: :rn:`5.5.27-29.0` |
361 |:Upstream fix: N/A |
362 +-------------------------------------------------------------------------------------------------------------+
363 |:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no. |
364 |:Launchpad bug: :bug:`1013432` |
365-|:Upstream state: Verified (checked on 2013-01-18) |
366+|:Upstream state: Verified (checked on 2013-02-21) |
367 |:Fix Released: :rn:`5.5.27-28.0` |
368 |:Upstream fix: N/A |
369 +-------------------------------------------------------------------------------------------------------------+
370 |:Upstream bug: :mysqlbug:`66301` - INSERT ... ON DUPLICATE KEY UPDATE + innodb_autoinc_lock_mode=1 is broken |
371 |:Launchpad bug: :bug:`1035225` |
372-|:Upstream state: Verified (checked on 2013-01-18) |
373+|:Upstream state: Verified (checked on 2013-02-21) |
374 |:Fix Released: :rn:`5.5.27-28.0` |
375 |:Upstream fix: N/A |
376 +-------------------------------------------------------------------------------------------------------------+
377 |:Upstream bug: :mysqlbug:`60743` - typo in cmake/dtrace.cmake |
378 |:Launchpad bug: :bug:`1013455` |
379-|:Upstream state: Verified (checked on 2013-01-18) |
380+|:Upstream state: Verified (checked on 2013-02-21) |
381 |:Fix Released: :rn:`5.5.25a-27.1` |
382 |:Upstream fix: N/A |
383 +-------------------------------------------------------------------------------------------------------------+
384 |:Upstream bug: :mysqlbug:`64663` - Segfault when adding indexes to InnoDB temporary tables |
385 |:Launchpad bug: :bug:`999147` |
386-|:Upstream state: Verified (checked on 2013-01-18) |
387+|:Upstream state: Verified (checked on 2013-02-21) |
388 |:Fix Released: :rn:`5.5.24-26.0` |
389 |:Upstream fix: N/A |
390 +-------------------------------------------------------------------------------------------------------------+
391@@ -109,7 +133,7 @@
392 +-------------------------------------------------------------------------------------------------------------+
393 |:Upstream bug: :mysqlbug:`64432` - Bug :mysqlbug:`54330` (Broken fast index creation) was never fixed in 5.5 |
394 |:Launchpad bug: :bug:`939485` |
395-|:Upstream state: Documenting (checked on 2013-01-18) |
396+|:Upstream state: Documenting (checked on 2013-02-21) |
397 |:Fix Released: :rn:`5.5.21-25.0` |
398 |:Upstream fix: N/A |
399 +-------------------------------------------------------------------------------------------------------------+
400@@ -133,7 +157,7 @@
401 +-------------------------------------------------------------------------------------------------------------+
402 |:Upstream bug: :mysqlbug:`62516` - Fast index creation does not update index statistics |
403 |:Launchpad bug: :bug:`857590` |
404-|:Upstream state: Verified (checked on 2013-01-18) |
405+|:Upstream state: Verified (checked on 2013-02-21) |
406 |:Fix Released: :rn:`5.5.16-22.0` |
407 |:Upstream fix: N/A |
408 +-------------------------------------------------------------------------------------------------------------+
409@@ -145,7 +169,7 @@
410 +-------------------------------------------------------------------------------------------------------------+
411 |:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |
412 |:Launchpad bug: :bug:`800035` |
413-|:Upstream state: Verified (checked on 2013-01-18) |
414+|:Upstream state: Verified (checked on 2013-02-21) |
415 |:Fix Released: :rn:`5.5.13-20.4` |
416 |:Upstream fix: N/A |
417 +-------------------------------------------------------------------------------------------------------------+

Subscribers

People subscribed via source and target branches