Percona Server moved to https://jira.percona.com/projects/PS

Merge lp:~hrvojem/percona-server/rn-5.6.22-72.0-5.6 into lp:percona-server/5.6

  1. rn-5.6.22-72.0-5.6
  2. Merge into 5.6
Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Laurynas Biveinis
Approved revision: no longer in the source branch.
Merged at revision: 737
Proposed branch: lp:~hrvojem/percona-server/rn-5.6.22-72.0-5.6
Merge into: lp:percona-server/5.6
Diff against target: 705 lines (+280/-46)
10 files modified
doc/source/conf.py (+1/-1)
doc/source/diagnostics/innodb_show_status.rst (+0/-2)
doc/source/diagnostics/response_time_distribution.rst (+43/-1)
doc/source/flexibility/online_gtid_deployment.rst (+69/-0)
doc/source/index.rst (+1/-0)
doc/source/release-notes/Percona-Server-5.6.22-72.0.rst (+32/-0)
doc/source/release-notes/release-notes_index.rst (+1/-0)
doc/source/tokudb/removing_tokudb.rst (+29/-1)
doc/source/tokudb/tokudb_installation.rst (+59/-2)
doc/source/upstream-bug-fixes.rst (+45/-39)
To merge this branch: bzr merge lp:~hrvojem/percona-server/rn-5.6.22-72.0-5.6
Reviewer Review Type Date Requested Status
Laurynas Biveinis (community) Approve
Review via email: mp+248785@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) :
review: Needs Fixing
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

What about upstream bug list update? Please also see the diff comments.

review: Needs Fixing
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) :
review: Needs Fixing
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) :
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 2015-01-12 08:11:31 +0000
3+++ doc/source/conf.py 2015-02-06 14:22:58 +0000
4@@ -54,7 +54,7 @@
5 # The short X.Y version.
6 version = '5.6'
7 # The full version, including alpha/beta/rc tags.
8-release = '5.6.22-71.0'
9+release = '5.6.22-72.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/diagnostics/innodb_show_status.rst'
15--- doc/source/diagnostics/innodb_show_status.rst 2014-12-01 07:53:48 +0000
16+++ doc/source/diagnostics/innodb_show_status.rst 2015-02-06 14:22:58 +0000
17@@ -8,8 +8,6 @@
18
19 This feature modified the ``SHOW ENGINE INNODB STATUS`` command as follows:
20
21- * ``TRANSACTION`` section was moved to the end of the output, so that important information is not overlooked when the there is a large amount of it.
22-
23 * Added two variables to control ``SHOW ENGINE INNODB STATUS`` information presented (bugfix for `#29123 <http://bugs.mysql.com/bug.php?id=29123>`_):
24
25 * :variable:`innodb_show_verbose_locks` - Whether to show records locked
26
27=== modified file 'doc/source/diagnostics/response_time_distribution.rst'
28--- doc/source/diagnostics/response_time_distribution.rst 2014-12-01 07:53:48 +0000
29+++ doc/source/diagnostics/response_time_distribution.rst 2015-02-06 14:22:58 +0000
30@@ -69,6 +69,19 @@
31
32 * 1 query with 10.000000 < query execution time < = 100.0000 seconds; total execution time of the 1 query = 55.937094 seconds
33
34+.. _rtd_rw_split:
35+
36+Logging the queries in separate ``READ`` and ``WRITE`` tables
37+=============================================================
38+
39+.. note::
40+
41+ This feature is considered **BETA** quality.
42+
43+|Percona Server| :rn:`5.6.22-72.0` is now able to log the queries response times into separate ``READ`` and ``WRITE`` ``INFORMATION_SCHEMA`` tables. The two new tables are named :table:`QUERY_RESPONSE_TIME_READ` and :table:`QUERY_RESPONSE_TIME_WRITE` respectively. The decision on whether a query is a ``read`` or a ``write`` is based on the type of the command. Thus, for example, an ``UPDATE ... WHERE <condition>`` is always logged as a ``write`` query even if ``<condition>`` is always false and thus no actual writes happen during its execution.
44+
45+Following SQL commands will be considered as ``WRITE`` queries and will be logged into the :table:`QUERY_RESPONSE_TIME_WRITE` table: ``CREATE_TABLE``, ``CREATE_INDEX``, ``ALTER_TABLE``, ``TRUNCATE``, ``DROP_TABLE``, ``LOAD``, ``CREATE_DB``, ``DROP_DB``, ``ALTER_DB``, ``RENAME_TABLE``, ``DROP_INDEX``, ``CREATE_VIEW``, ``DROP_VIEW``, ``CREATE_TRIGGER``, ``DROP_TRIGGER``, ``CREATE_EVENT``, ``ALTER_EVENT``, ``DROP_EVENT``, ``UPDATE``, ``UPDATE_MULTI``, ``INSERT``, ``INSERT_SELECT``, ``DELETE``, ``DELETE_MULTI``, ``REPLACE``, ``REPLACE_SELECT``, ``CREATE_USER``, ``RENAME_USER``, ``DROP_USER``, ``ALTER_USER``, ``GRANT``, ``REVOKE``, ``REVOKE_ALL``, ``OPTIMIZE``, ``CREATE_FUNCTION``, ``CREATE_PROCEDURE``, ``CREATE_SPFUNCTION``, ``DROP_PROCEDURE``, ``DROP_FUNCTION``, ``ALTER_PROCEDURE``, ``ALTER_FUNCTION``, ``INSTALL_PLUGIN``, and ``UNINSTALL_PLUGIN``. Commands not listed here are considered as ``READ`` queries and will be logged into the :table:`QUERY_RESPONSE_TIME_READ` table.
46+
47 Installing the plugins
48 ======================
49
50@@ -86,6 +99,18 @@
51
52 This plugin provides the interface (:table:`QUERY_RESPONSE_TIME`) to output gathered statistics.
53
54+.. code-block:: mysql
55+
56+ mysql> INSTALL PLUGIN QUERY_RESPONSE_TIME_READ SONAME 'query_response_time.so';
57+
58+This plugin provides the interface (:table:`QUERY_RESPONSE_TIME_READ`) to output gathered statistics. **NOTE:** Available in |Percona Server| :rn:`5.6.22-72.0` or later.
59+
60+.. code-block:: mysql
61+
62+ mysql> INSTALL PLUGIN QUERY_RESPONSE_TIME_WRITE SONAME 'query_response_time.so';
63+
64+This plugin provides the interface (:table:`QUERY_RESPONSE_TIME_WRITE`) to output gathered statistics. **NOTE:** Available in |Percona Server| :rn:`5.6.22-72.0` or later.
65+
66 You can check if plugins are installed correctly by running:
67
68 .. code-block:: mysql
69@@ -95,6 +120,8 @@
70 ...
71 | QUERY_RESPONSE_TIME | ACTIVE | INFORMATION SCHEMA | query_response_time.so | GPL |
72 | QUERY_RESPONSE_TIME_AUDIT | ACTIVE | AUDIT | query_response_time.so | GPL |
73+ | QUERY_RESPONSE_TIME_READ | ACTIVE | INFORMATION SCHEMA | query_response_time.so | GPL |
74+ | QUERY_RESPONSE_TIME_WRITE | ACTIVE | INFORMATION SCHEMA | query_response_time.so | GPL |
75 +-----------------------------+----------+--------------------+------------------------+---------+
76
77 Usage
78@@ -147,7 +174,7 @@
79
80 ``FLUSH`` does two things:
81
82- * Clears the collected times from the :table:`QUERY_RESPONSE_TIME` table
83+ * Clears the collected times from the :table:`QUERY_RESPONSE_TIME`, :table:`QUERY_RESPONSE_TIME_READ`, and :table:`QUERY_RESPONSE_TIME_WRITE` tables
84
85 * Reads the value of :variable:`query_response_time_range_base` and uses it to set the range base for the table
86
87@@ -169,6 +196,9 @@
88 * :rn:`5.6.21-69.0`:
89 Feature ported from |Percona Server| 5.5 as a plugin
90
91+ * :rn:`5.6.22-72.0`:
92+ Implemented query logging based on ``READ`` and ``WRITE`` queries.
93+
94 System Variables
95 ================
96
97@@ -224,3 +254,15 @@
98 :column INT(11) COUNT: Number of queries with execution times that fell into that interval
99 :column VARCHAR TOTAL: Total execution time of the queries
100
101+.. table:: INFORMATION_SCHEMA.QUERY_RESPONSE_TIME_READ
102+
103+ :column VARCHAR TIME: Interval range in which the query occurred
104+ :column INT(11) COUNT: Number of queries with execution times that fell into that interval
105+ :column VARCHAR TOTAL: Total execution time of the queries
106+
107+.. table:: INFORMATION_SCHEMA.QUERY_RESPONSE_TIME_WRITE
108+
109+ :column VARCHAR TIME: Interval range in which the query occurred
110+ :column INT(11) COUNT: Number of queries with execution times that fell into that interval
111+ :column VARCHAR TOTAL: Total execution time of the queries
112+
113
114=== added file 'doc/source/flexibility/online_gtid_deployment.rst'
115--- doc/source/flexibility/online_gtid_deployment.rst 1970-01-01 00:00:00 +0000
116+++ doc/source/flexibility/online_gtid_deployment.rst 2015-02-06 14:22:58 +0000
117@@ -0,0 +1,69 @@
118+.. _online_gtid_deployment:
119+
120+========================
121+ Online GTID deployment
122+========================
123+
124+|Percona Server| now supports Online GTID deployment. This enables GTID to be deployed on existing replication setups without making the master read-only and stopping all the slaves. This feature was ported from the *Facebook* branch. Before this feature was implemented deploying the GTID replication on already existing replication setups required making a master :variable:`read_only`, shutting down all |MySQL| instances in the replica set simultaneously at the same position, enabling the :variable:`gtid_mode` variable in :file:`my.cnf`, and then starting all of the instances.
125+
126+With :variable:`gtid_deployment_step` enabled, a host cannot generate GTID values on its own, but if GTID logged events are received through replication stream from master, they will be logged.
127+
128+Performing the online GTID deployment
129+=====================================
130+
131+The online GTID deployment procedure can be done with the following steps:
132+
133+1) replicas: :variable:`gtid_mode` = ``ON`` and :variable:`gtid_deployment_step` = ``ON``
134+
135+ master: :variable:`gtid_mode` = ``OFF`` and :variable:`gtid_deployment_step` = ``OFF``
136+
137+On each replica, one at a time, restart the |MySQL| server to enable :variable:`gtid_mode` and :variable:`gtid_deployment_step`. Afterward, we are in a state where every replica has :variable:`gtid_mode` set to ``ON`` and :variable:`gtid_deployment_step` set to ``ON``, but the master still has :variable:`gtid_mode` set to ``OFF`` and :variable:`gtid_deployment_step` set to ``OFF``. **NOTE:** in order to successfully restart the slaves :variable:`enforce-gtid-consistency` needs to be enabled as well.
138+
139+2) new master: :variable:`gtid_mode` = ``ON`` and :variable:`gtid_deployment_step` = ``OFF``
140+
141+ rest of the replicas: :variable:`gtid_mode` = ``ON`` and :variable:`gtid_deployment_step` = ``ON``
142+
143+ old master: :variable:`gtid_mode` = ``OFF`` and :variable:`gtid_deployment_step` = ``OFF``
144+
145+Perform a master promotion as normal, i.e. set the :variable:`gtid_mode` to ``ON`` and :variable:`gtid_deployment_step` to ``OFF``, re-pointing the replicas and original master to the new master. The original master's replication will intentionally break when started, since it still has the variable :variable:`gtid_mode` set to ``OFF`` and :variable:`gtid_deployment_step` to ``OFF``.
146+
147+3) new master: :variable:`gtid_mode` = ``ON`` and :variable:`gtid_deployment_step` = ``OFF``
148+
149+ rest of the replicas: :variable:`gtid_mode` = ``ON``
150+
151+ old master: :variable:`gtid_mode` = ``ON``
152+
153+Restart the original master to enable :variable:`gtid_mode`. It will now be able to replicate from the new master, and the entire replica set now has :variable:`gtid_mode` set to ``ON``. You can now set the :variable:`gtid_deployment_step` to ``OFF``.
154+
155+Version Specific Information
156+============================
157+
158+ * :rn:`5.6.22-72.0`:
159+ Feature ported from the *Facebook* `branch <https://github.com/facebook/mysql-5.6>`_
160+
161+System Variables
162+================
163+
164+.. variable:: gtid_deployment_step
165+
166+ :version 5.6.22-72.0: Introduced.
167+ :cli: Yes
168+ :conf: Yes
169+ :scope: Global
170+ :dyn: Yes
171+ :default: OFF
172+
173+When this variable is enabled, a host cannot generate GTIDs on its own, but if GTID logged events are received through replication stream from the master, they will be logged.
174+
175+The conditions for dynamic switching the :variable:`gtid_deployment_step` off are the same as for `read_only <http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_read_only>`_ variable:
176+
177+ 1) If you attempt to enable :variable:`gtid_deployment_step` while you have any explicit locks (acquired with ``LOCK TABLES``) or have a pending transaction, an error occurs.
178+
179+ 2) If you attempt to enable :variable:`gtid_deployment_step` while other clients hold explicit table locks or have pending transactions, the attempt blocks until the locks are released and the transactions end. While the attempt to enable :variable:`gtid_deployment_step` is pending, requests by other clients for table locks or to begin transactions also block until :variable:`gtid_deployment_step` has been set.
180+
181+Related Reading
182+===============
183+
184+ * `Lessons from Deploying MySQL GTID at Scale <https://www.facebook.com/notes/mysql-at-facebook/lessons-from-deploying-mysql-gtid-at-scale/10152252699590933>`_
185+ * |MySQL| `GTID documentation <https://dev.mysql.com/doc/refman/5.6/en/replication-gtids.html>`_
186+
187
188=== modified file 'doc/source/index.rst'
189--- doc/source/index.rst 2015-01-09 15:11:15 +0000
190+++ doc/source/index.rst 2015-02-06 14:22:58 +0000
191@@ -94,6 +94,7 @@
192 flexibility/slowlog_rotation
193 flexibility/mysqlbinlog_change_db
194 flexibility/csv_engine_mode
195+ flexibility/online_gtid_deployment
196
197 Reliability Improvements
198 ========================
199
200=== added file 'doc/source/release-notes/Percona-Server-5.6.22-72.0.rst'
201--- doc/source/release-notes/Percona-Server-5.6.22-72.0.rst 1970-01-01 00:00:00 +0000
202+++ doc/source/release-notes/Percona-Server-5.6.22-72.0.rst 2015-02-06 14:22:58 +0000
203@@ -0,0 +1,32 @@
204+.. rn:: 5.6.22-72.0
205+
206+==============================
207+ |Percona Server| 5.6.22-72.0
208+==============================
209+
210+Percona is glad to announce the release of |Percona Server| 5.6.22-72.0 on February 6th, 2015 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.22-72.0/>`_ and from the :doc:`Percona Software Repositories </installation>`).
211+
212+Based on `MySQL 5.6.22 <http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-22.html>`_, including all the bug fixes in it, |Percona Server| 5.6.22-72.0 is the current GA release in the |Percona Server| 5.6 series. All of |Percona|'s software is open-source and free, all the details of the release can be found in the `5.6.22-72.0 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.6.22-72.0>`_.
213+
214+New Features
215+============
216+
217+ |Percona Server| is now able to log the query's response times into :ref:`separate <rtd_rw_split>` ``READ`` and ``WRITE`` ``INFORMATION_SCHEMA`` tables. Two new ``INFORMATION_SCHEMA`` tables :table:`QUERY_RESPONSE_TIME_READ` and :table:`QUERY_RESPONSE_TIME_WRITE` have been implemented for ``READ`` and ``WRITE`` queries correspondingly.
218+
219+ New ``ps_tokudb_admin`` script has been implemented to make the TokuDB Storage engine installation :ref:`easier <tokudb_quick_install>`.
220+
221+ |Percona Server| now supports :ref:`online_gtid_deployment`. This enables GTID to be deployed on existing replication setups without making the master ``read-only`` and stopping all the slaves. This feature was ported from the Facebook `branch <https://github.com/facebook/mysql-5.6>`_.
222+
223+Bugs Fixed
224+==========
225+
226+ ``SET STATEMENT ... FOR <statement>`` would crash the server if it could not execute the ``<statement>`` due to: 1) if the ``<statement>`` was Read-Write in a Read-Only transaction (bug :bug:`1387951`), 2) if the ``<statement>`` needed to re-open an already open temporary table and would fail to do so (bug :bug:`1412423`), 3) if the ``<statement>`` needed to commit implicitly the ongoing transaction and the implicit commit would fail (bug :bug:`1418049`).
227+
228+ TokuDB storage engine would fail to load after the upgrade on *CentOS* 5 and 6. Bug fixed :bug:`1413956`.
229+
230+ Fixed a potential low-probability crash in |XtraDB| linear read-ahead code. Bug fixed :bug:`1417953`.
231+
232+ Setting the :variable:`max_statement_time` per query had no effect. Bug fixed :bug:`1376934`.
233+
234+Other bugs fixed: :bug:`1407941`, :bug:`1415843` (upstream :mysqlbug:`75642`).
235+
236
237=== modified file 'doc/source/release-notes/release-notes_index.rst'
238--- doc/source/release-notes/release-notes_index.rst 2015-01-12 08:11:31 +0000
239+++ doc/source/release-notes/release-notes_index.rst 2015-02-06 14:22:58 +0000
240@@ -6,6 +6,7 @@
241 :maxdepth: 1
242 :glob:
243
244+ Percona-Server-5.6.22-72.0
245 Percona-Server-5.6.22-71.0
246 Percona-Server-5.6.21-70.1
247 Percona-Server-5.6.21-70.0
248
249=== modified file 'doc/source/tokudb/removing_tokudb.rst'
250--- doc/source/tokudb/removing_tokudb.rst 2014-10-10 09:34:04 +0000
251+++ doc/source/tokudb/removing_tokudb.rst 2015-02-06 14:22:58 +0000
252@@ -22,7 +22,35 @@
253 Removing the plugins
254 --------------------
255
256-Storage engine requires manual removal:
257+If you're using |Percona Server| :rn:`5.6.22-72.0` or later you can use the ``ps_tokudb_admin`` script to remove the plugins:
258+
259+.. code-block:: bash
260+
261+ ps_tokudb_admin --disable -uroot -pPassw0rd
262+
263+Script output should look like this:
264+
265+.. code-block:: bash
266+
267+ Checking if Percona server is running with jemalloc enabled...
268+ >> Percona server is running with jemalloc enabled.
269+
270+ Checking transparent huge pages status on the system...
271+ >> Transparent huge pages are currently disabled on the system.
272+
273+ Checking if thp-setting=never option is already set in config file...
274+ >> Option thp-setting=never is set in the config file.
275+
276+ Checking TokuDB plugin status...
277+ >> TokuDB plugin is installed.
278+
279+ Removing thp-setting=never option from /etc/mysql/my.cnf
280+ >> Successfuly removed thp-setting=never option from /etc/mysql/my.cnf
281+
282+ Uninstalling TokuDB plugin...
283+ >> Successfuly uninstalled TokuDB plugin.
284+
285+Prior to |Percona Server| :rn:`5.6.22-72.0` TokuDB storage engine requires manual removal:
286
287 .. code-block:: mysql
288
289
290=== modified file 'doc/source/tokudb/tokudb_installation.rst'
291--- doc/source/tokudb/tokudb_installation.rst 2014-09-22 13:27:26 +0000
292+++ doc/source/tokudb/tokudb_installation.rst 2015-02-06 14:22:58 +0000
293@@ -71,11 +71,66 @@
294
295 root@wheezy:~# apt-get install percona-server-tokudb-5.6
296
297+.. _tokudb_quick_install:
298
299 Enabling the TokuDB Storage Engine
300 ==================================
301
302-This storage engine requires manual installation if there is a root password already set up during the new installation or upgrade.
303+Once the TokuDB server package has been installed following output will be shown:
304+
305+.. code-block:: bash
306+
307+ * This release of Percona Server is distributed with TokuDB storage engine.
308+ * Run the following script to enable the TokuDB storage engine in Percona Server:
309+
310+ ps_tokudb_admin --enable -u <mysql_admin_user> -p[mysql_admin_pass] [-S <socket>] [-h <host> -P <port>]
311+
312+ * See http://www.percona.com/doc/percona-server/5.6/tokudb/tokudb_installation.html for more installation details
313+
314+ * See http://www.percona.com/doc/percona-server/5.6/tokudb/tokudb_intro.html for an introduction to TokuDB
315+
316+|Percona Server| :rn:`5.6.22-72.0` has implemented ``ps_tokudb_admin`` script to make the enabling the TokuDB storage engine easier. This script will automatically disable Transparent huge pages, if they're enabled, and install the TokuDB storage engine with all the required plugins. After you run the script with required parameters:
317+
318+.. code-block:: bash
319+
320+ ps_tokudb_admin --enable -uroot -pPassw0rd
321+
322+Following output will be displayed:
323+
324+.. code-block:: bash
325+
326+ Checking if Percona server is running with jemalloc enabled...
327+ >> Percona server is running with jemalloc enabled.
328+
329+ Checking transparent huge pages status on the system...
330+ >> Transparent huge pages are currently disabled on the system.
331+
332+ Checking if thp-setting=never option is already set in config file...
333+ >> Option thp-setting=never is not set in the config file.
334+ >> (needed only if THP is not disabled permanently on the system)
335+
336+ Checking TokuDB plugin status...
337+ >> TokuDB plugin is not installed.
338+
339+ Adding thp-setting=never option into /etc/mysql/my.cnf
340+ >> Successfuly added thp-setting=never option into /etc/mysql/my.cnf
341+
342+ Installing TokuDB engine...
343+ >> Successfuly installed TokuDB plugin.
344+
345+If the script returns no errors, TokuDB storage engine should be successfully enabled on your server. You can check it out by running:
346+
347+.. code-block:: mysql
348+
349+ mysql> SHOW ENGINES;
350+ ...
351+ | TokuDB | YES | Tokutek TokuDB Storage Engine with Fractal Tree(tm) Technology | YES | YES | YES |
352+ ...
353+
354+Enabling the TokuDB Storage Engine Manually
355+===========================================
356+
357+If you're running |Percona Server| :rn:`5.6.22-71.0` this storage engine requires manual installation.
358
359 .. code-block:: mysql
360
361@@ -122,7 +177,7 @@
362 +------------------+
363 | @@tokudb_version |
364 +------------------+
365- | tokudb-7.1.7-rc7 |
366+ | tokudb-7.5.4 |
367 +------------------+
368 1 row in set (0.00 sec)
369
370@@ -139,6 +194,8 @@
371 TokuDB storage engine available as a separate |Percona Server| package.
372 * :rn:`5.6.19-67.0`
373 TokuDB storage engine is considered GA quality.
374+ * :rn:`5.6.22-72.0`
375+ Implemented ``ps_tokudb_admin`` script to make the installation :ref:`easier <tokudb_quick_install>`
376
377
378 Other Reading
379
380=== modified file 'doc/source/upstream-bug-fixes.rst'
381--- doc/source/upstream-bug-fixes.rst 2015-01-12 08:11:31 +0000
382+++ doc/source/upstream-bug-fixes.rst 2015-02-06 14:22:58 +0000
383@@ -5,9 +5,15 @@
384 =============================================================
385
386 +-------------------------------------------------------------------------------------------------------------+
387+|:Upstream bug: :mysqlbug:`75642` - Extend valid range of dummy certificates ni mysql-test/std_data |
388+|:Launchpad bug: :bug:`1415843` |
389+|:Upstream state: Verified (checked on 2015-02-06) |
390+|:Fix Released: :rn:`5.6.22-72.0` |
391+|:Upstream fix: N/A |
392++-------------------------------------------------------------------------------------------------------------+
393 |:Upstream bug: :mysqlbug:`73979` - wrong stack size calculation leads to stack overflow in pinbox allocator |
394 |:Launchpad bug: :bug:`1351148` |
395-|:Upstream state: In Progress (checked on 2015-01-12) |
396+|:Upstream state: In Progress (checked on 2015-02-06) |
397 |:Fix Released: :rn:`5.6.22-71.0` |
398 |:Upstream fix: N/A |
399 +-------------------------------------------------------------------------------------------------------------+
400@@ -19,49 +25,49 @@
401 +-------------------------------------------------------------------------------------------------------------+
402 |:Upstream bug: :mysqlbug:`57430` - query optimizer does not pick covering index for some "order by" queries |
403 |:Launchpad bug: :bug:`1394967` |
404-|:Upstream state: Verified (checked on 2015-01-12) |
405+|:Upstream state: Verified (checked on 2015-02-06) |
406 |:Fix Released: :rn:`5.6.22-71.0` |
407 |:Upstream fix: N/A |
408 +-------------------------------------------------------------------------------------------------------------+
409 |:Upstream bug: :mysqlbug:`74987` - mtr failure on Ubuntu Utopic, mysqlhotcopy fails with wrong error(255) |
410 |:Launchpad bug: :bug:`1396330` |
411-|:Upstream state: Verified (checked on 2015-01-12) |
412+|:Upstream state: Verified (checked on 2015-02-06) |
413 |:Fix Released: :rn:`5.6.22-71.0` |
414 |:Upstream fix: N/A |
415 +-------------------------------------------------------------------------------------------------------------+
416 |:Upstream bug: :mysqlbug:`75189` - engines suite tests depending on InnoDB implementation details |
417 |:Launchpad bug: :bug:`1401776` |
418-|:Upstream state: Verified (checked on 2015-01-12) |
419+|:Upstream state: Verified (checked on 2015-02-06) |
420 |:Fix Released: :rn:`5.6.22-71.0` |
421 |:Upstream fix: N/A |
422 +-------------------------------------------------------------------------------------------------------------+
423 |:Upstream bug: :mysqlbug:`72475` - Binlog events with binlog_format=MIXED are unconditionally logged in ROW..|
424 |:Launchpad bug: :bug:`1313901` |
425-|:Upstream state: Verified (checked on 2015-01-12) |
426+|:Upstream state: Verified (checked on 2015-02-06) |
427 |:Fix Released: :rn:`5.6.21-70.1` |
428 |:Upstream fix: N/A |
429 +-------------------------------------------------------------------------------------------------------------+
430 |:Upstream bug: :mysqlbug:`74842` - Incorrect attribute((nonnull)) for btr_cur_ins_lock_and_undo callees |
431 |:Launchpad bug: :bug:`1390695` |
432-|:Upstream state: Open (checked on 2015-01-12) |
433+|:Upstream state: Open (checked on 2015-02-06) |
434 |:Fix Released: :rn:`5.6.21-70.1` |
435 |:Upstream fix: N/A |
436 +-------------------------------------------------------------------------------------------------------------+
437 |:Upstream bug: :mysqlbug:`74440` - mysql_install_db not handling mysqld startup failure |
438 |:Launchpad bug: :bug:`1382782` |
439-|:Upstream state: Verified (checked on 2015-01-12) |
440+|:Upstream state: Verified (checked on 2015-02-06) |
441 |:Fix Released: :rn:`5.6.21-70.0` |
442 |:Upstream fix: N/A |
443 +-------------------------------------------------------------------------------------------------------------+
444 |:Upstream bug: :mysqlbug:`73066` - Replication stall with multi-threaded replication |
445 |:Launchpad bug: :bug:`1331586` |
446-|:Upstream state: Verified (checked on 2015-01-12) |
447+|:Upstream state: Verified (checked on 2015-02-06) |
448 |:Fix Released: :rn:`5.6.21-70.0` |
449 |:Upstream fix: N/A |
450 +-------------------------------------------------------------------------------------------------------------+
451 |:Upstream bug: :mysqlbug:`71091` - CSV engine does not properly process ``""``, in quotes |
452 |:Launchpad bug: :bug:`1316042` |
453-|:Upstream state: Verified (checked on 2015-01-12) |
454+|:Upstream state: Verified (checked on 2015-02-06) |
455 |:Fix Released: :rn:`5.6.21-70.0` |
456 |:Upstream fix: N/A |
457 +-------------------------------------------------------------------------------------------------------------+
458@@ -73,7 +79,7 @@
459 +-------------------------------------------------------------------------------------------------------------+
460 |:Upstream bug: :mysqlbug:`73418` - Add --manual-lldb option to mysql-test-run.pl |
461 |:Launchpad bug: :bug:`1328482` |
462-|:Upstream state: Verified (checked on 2015-01-12) |
463+|:Upstream state: Verified (checked on 2015-02-06) |
464 |:Fix Released: :rn:`5.6.20-68.0` |
465 |:Upstream fix: N/A |
466 +-------------------------------------------------------------------------------------------------------------+
467@@ -91,13 +97,13 @@
468 +-------------------------------------------------------------------------------------------------------------+
469 |:Upstream bug: :mysqlbug:`72615` - MTR --mysqld=--default-storage-engine=foo incompatible w/ dynamically... |
470 |:Launchpad bug: :bug:`1318537` |
471-|:Upstream state: Verified (checked on 2015-01-12) |
472+|:Upstream state: Verified (checked on 2015-02-06) |
473 |:Fix Released: :rn:`5.6.17-66.0` |
474 |:Upstream fix: N/A |
475 +-------------------------------------------------------------------------------------------------------------+
476 |:Upstream bug: :mysqlbug:`72163` - Rev 5774 broke rpl_plugin_load |
477 |:Launchpad bug: :bug:`1299688` |
478-|:Upstream state: Verified (checked on 2015-01-12) |
479+|:Upstream state: Verified (checked on 2015-02-06) |
480 |:Fix Released: :rn:`5.6.17-65.0` |
481 |:Upstream fix: N/A |
482 +-------------------------------------------------------------------------------------------------------------+
483@@ -115,19 +121,19 @@
484 +-------------------------------------------------------------------------------------------------------------+
485 |:Upstream bug: :mysqlbug:`71374` - Slave IO thread won't attempt auto reconnect to the master/error-code 1159|
486 |:Launchpad bug: :bug:`1268729` |
487-|:Upstream state: Verified (checked on 2015-01-12) |
488+|:Upstream state: Verified (checked on 2015-02-06) |
489 |:Fix Released: :rn:`5.6.16-64.1` |
490 |:Upstream fix: N/A |
491 +-------------------------------------------------------------------------------------------------------------+
492 |:Upstream bug: :mysqlbug:`71988` - page_cleaner: aggressive background flushing |
493 |:Launchpad bug: :bug:`1238039` |
494-|:Upstream state: Verified (checked on 2015-01-12) |
495+|:Upstream state: Verified (checked on 2015-02-06) |
496 |:Fix Released: :rn:`5.6.16-64.0` |
497 |:Upstream fix: N/A |
498 +-------------------------------------------------------------------------------------------------------------+
499 |:Upstream bug: :mysqlbug:`71624` - printf size_t results in a fatal warning in 32-bit debug builds |
500 |:Launchpad bug: :bug:`1277505` |
501-|:Upstream state: Can't repeat (checked on 2015-01-12) |
502+|:Upstream state: Can't repeat (checked on 2015-02-06) |
503 |:Fix Released: :rn:`5.6.16-64.0` |
504 |:Upstream fix: N/A |
505 +-------------------------------------------------------------------------------------------------------------+
506@@ -169,13 +175,13 @@
507 +-------------------------------------------------------------------------------------------------------------+
508 |:Upstream bug: :mysqlbug:`71270` - Failures to end bulk insert for partitioned tables handled incorrectly |
509 |:Launchpad bug: :bug:`1204871` |
510-|:Upstream state: Verified (checked on 2015-01-12) |
511+|:Upstream state: Verified (checked on 2015-02-06) |
512 |:Fix Released: :rn:`5.6.16-64.0` |
513 |:Upstream fix: N/A |
514 +-------------------------------------------------------------------------------------------------------------+
515 |:Upstream bug: :mysqlbug:`71217` - Threadpool - add thd_wait_begin/thd_wait_end to the network IO functions |
516 |:Launchpad bug: :bug:`1159743` |
517-|:Upstream state: Open (checked on 2015-01-12) |
518+|:Upstream state: Open (checked on 2015-02-06) |
519 |:Fix Released: :rn:`5.6.15-63.0` |
520 |:Upstream fix: N/A |
521 +-------------------------------------------------------------------------------------------------------------+
522@@ -193,7 +199,7 @@
523 +-------------------------------------------------------------------------------------------------------------+
524 |:Upstream bug: :mysqlbug:`71411` - buf_flush_LRU() does not return correct number in case of compressed pages|
525 |:Launchpad bug: :bug:`1231918` |
526-|:Upstream state: Verified (checked on 2015-01-12) |
527+|:Upstream state: Verified (checked on 2015-02-06) |
528 |:Fix Released: :rn:`5.6.13-61.0` |
529 |:Upstream fix: N/A |
530 +-------------------------------------------------------------------------------------------------------------+
531@@ -205,7 +211,7 @@
532 +-------------------------------------------------------------------------------------------------------------+
533 |:Upstream bug: :mysqlbug:`70490` - Suppression is too strict on some systems |
534 |:Launchpad bug: :bug:`1205196` |
535-|:Upstream state: No Feedback (checked on 2015-01-12) |
536+|:Upstream state: No Feedback (checked on 2015-02-06) |
537 |:Fix Released: :rn:`5.6.13-61.0` |
538 |:Upstream fix: N/A |
539 +-------------------------------------------------------------------------------------------------------------+
540@@ -217,7 +223,7 @@
541 +-------------------------------------------------------------------------------------------------------------+
542 |:Upstream bug: :mysqlbug:`70500` - Page cleaner should perform LRU flushing regardless of server activity |
543 |:Launchpad bug: :bug:`1234562` |
544-|:Upstream state: Verified (checked on 2015-01-12) |
545+|:Upstream state: Verified (checked on 2015-02-06) |
546 |:Fix Released: :rn:`5.6.13-61.0` |
547 |:Upstream fix: N/A |
548 +-------------------------------------------------------------------------------------------------------------+
549@@ -235,25 +241,25 @@
550 +-------------------------------------------------------------------------------------------------------------+
551 |:Upstream bug: :mysqlbug:`68481` - InnoDB LRU flushing for MySQL 5.6 needs work |
552 |:Launchpad bug: :bug:`1232406` |
553-|:Upstream state: Verified (checked on 2015-01-12) |
554+|:Upstream state: Verified (checked on 2015-02-06) |
555 |:Fix Released: :rn:`5.6.13-61.0` |
556 |:Upstream fix: N/A |
557 +-------------------------------------------------------------------------------------------------------------+
558 |:Upstream bug: :mysqlbug:`70453` - Add hard timeouts to page cleaner flushes |
559 |:Launchpad bug: :bug:`1232101` |
560-|:Upstream state: Verified (checked on 2015-01-12) |
561+|:Upstream state: Verified (checked on 2015-02-06) |
562 |:Fix Released: :rn:`5.6.13-61.0` |
563 |:Upstream fix: N/A |
564 +-------------------------------------------------------------------------------------------------------------+
565 |:Upstream bug: :mysqlbug:`69170` - buf_flush_LRU is lazy |
566 |:Launchpad bug: :bug:`1231918` |
567-|:Upstream state: Verified (checked on 2015-01-12) |
568+|:Upstream state: Verified (checked on 2015-02-06) |
569 |:Fix Released: :rn:`5.6.13-61.0` |
570 |:Upstream fix: N/A |
571 +-------------------------------------------------------------------------------------------------------------+
572 |:Upstream bug: :mysqlbug:`68555` - thread convoys from log_checkpoint_margin with innodb_buffer_pool_inst... |
573 |:Launchpad bug: :bug:`1236884` |
574-|:Upstream state: Verified (checked on 2015-01-12) |
575+|:Upstream state: Verified (checked on 2015-02-06) |
576 |:Fix Released: :rn:`5.6.13-61.0` |
577 |:Upstream fix: N/A |
578 +-------------------------------------------------------------------------------------------------------------+
579@@ -283,7 +289,7 @@
580 +-------------------------------------------------------------------------------------------------------------+
581 |:Upstream bug: :mysqlbug:`62018` - innodb adaptive hash index mutex contention |
582 |:Launchpad bug: :bug:`1216804` |
583-|:Upstream state: Verified (checked on 2015-01-12) |
584+|:Upstream state: Verified (checked on 2015-02-06) |
585 |:Fix Released: :rn:`5.6.13-60.6` |
586 |:Upstream fix: N/A |
587 +-------------------------------------------------------------------------------------------------------------+
588@@ -301,13 +307,13 @@
589 +-------------------------------------------------------------------------------------------------------------+
590 |:Upstream bug: :mysqlbug:`42415` - UPDATE/DELETE with LIMIT clause unsafe for SBL even with ORDER BY PK ... |
591 |:Launchpad bug: :bug:`1132194` |
592-|:Upstream state: Verified (checked on 2015-01-12) |
593+|:Upstream state: Verified (checked on 2015-02-06) |
594 |:Fix Released: :rn:`5.6.13-60.5` |
595 |:Upstream fix: N/A |
596 +-------------------------------------------------------------------------------------------------------------+
597 |:Upstream bug: :mysqlbug:`69639` - mysql failed to build with dtrace Sun D 1.11 |
598 |:Launchpad bug: :bug:`1196460` |
599-|:Upstream state: Open (checked on 2015-01-12) |
600+|:Upstream state: Open (checked on 2015-02-06) |
601 |:Fix Released: :rn:`5.6.13-60.5` |
602 |:Upstream fix: N/A |
603 +-------------------------------------------------------------------------------------------------------------+
604@@ -325,7 +331,7 @@
605 +-------------------------------------------------------------------------------------------------------------+
606 |:Upstream bug: :mysqlbug:`69856` - mysql_install_db does not function properly in 5.6 for debug builds |
607 |:Launchpad bug: :bug:`1179359` |
608-|:Upstream state: Verified (checked on 2015-01-12) |
609+|:Upstream state: Verified (checked on 2015-02-06) |
610 |:Fix Released: :rn:`5.6.12-60.4` |
611 |:Upstream fix: N/A |
612 +-------------------------------------------------------------------------------------------------------------+
613@@ -337,7 +343,7 @@
614 +-------------------------------------------------------------------------------------------------------------+
615 |:Upstream bug: :mysqlbug:`71183` - os_file_fsync() should handle fsync() returning EINTR |
616 |:Launchpad bug: :bug:`1262651` |
617-|:Upstream state: Verified (checked on 2015-01-12) |
618+|:Upstream state: Verified (checked on 2015-02-06) |
619 |:Fix Released: :rn:`5.6.11-60.3` |
620 |:Upstream fix: N/A |
621 +-------------------------------------------------------------------------------------------------------------+
622@@ -367,7 +373,7 @@
623 +-------------------------------------------------------------------------------------------------------------+
624 |:Upstream bug: :mysqlbug:`68714` - Remove literal statement digest values from perfschema tests |
625 |:Launchpad bug: :bug:`1157078` |
626-|:Upstream state: Verified (checked on 2015-01-12) |
627+|:Upstream state: Verified (checked on 2015-02-06) |
628 |:Fix Released: :rn:`5.6.11-60.3` |
629 |:Upstream fix: N/A |
630 +-------------------------------------------------------------------------------------------------------------+
631@@ -397,7 +403,7 @@
632 +-------------------------------------------------------------------------------------------------------------+
633 |:Upstream bug: :mysqlbug:`68713` - create_duplicate_weedout_tmp_table() leaves key_part_flag uninitialized |
634 |:Launchpad bug: :bug:`1157037` |
635-|:Upstream state: Verified (checked on 2015-01-12) |
636+|:Upstream state: Verified (checked on 2015-02-06) |
637 |:Fix Released: :rn:`5.6.11-60.3` |
638 |:Upstream fix: N/A |
639 +-------------------------------------------------------------------------------------------------------------+
640@@ -409,13 +415,13 @@
641 +-------------------------------------------------------------------------------------------------------------+
642 |:Upstream bug: :mysqlbug:`68999` - SSL_OP_NO_COMPRESSION not defined |
643 |:Launchpad bug: :bug:`1183610` |
644-|:Upstream state: No Feedback (checked on 2015-01-12) |
645+|:Upstream state: No Feedback (checked on 2015-02-06) |
646 |:Fix Released: :rn:`5.6.11-60.3` |
647 |:Upstream fix: N/A |
648 +-------------------------------------------------------------------------------------------------------------+
649 |:Upstream bug: :mysqlbug:`68845` - Unnecessary log_sys->mutex reacquisition in mtr_log_reserve_and_write() |
650 |:Launchpad bug: :bug:`1163439` |
651-|:Upstream state: Verified (checked on 2015-01-12) |
652+|:Upstream state: Verified (checked on 2015-02-06) |
653 |:Fix Released: :rn:`5.6.11-60.3` |
654 |:Upstream fix: N/A |
655 +-------------------------------------------------------------------------------------------------------------+
656@@ -505,7 +511,7 @@
657 +-------------------------------------------------------------------------------------------------------------+
658 |:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|
659 |:Launchpad bug: :bug:`1042517` |
660-|:Upstream state: Verified (checked on 2015-01-12) |
661+|:Upstream state: Verified (checked on 2015-02-06) |
662 |:Fix Released: :rn:`5.6.11-60.3` |
663 |:Upstream fix: N/A |
664 +-------------------------------------------------------------------------------------------------------------+
665@@ -517,7 +523,7 @@
666 +-------------------------------------------------------------------------------------------------------------+
667 |:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no. |
668 |:Launchpad bug: :bug:`1013432` |
669-|:Upstream state: Verified (checked on 2015-01-12) |
670+|:Upstream state: Verified (checked on 2015-02-06) |
671 |:Fix Released: :rn:`5.6.11-60.3` |
672 |:Upstream fix: N/A |
673 +-------------------------------------------------------------------------------------------------------------+
674@@ -547,13 +553,13 @@
675 +-------------------------------------------------------------------------------------------------------------+
676 |:Upstream bug: :mysqlbug:`25007` - memory tables with dynamic rows format |
677 |:Launchpad bug: :bug:`1148822` |
678-|:Upstream state: Verified (checked on 2015-01-12) |
679+|:Upstream state: Verified (checked on 2015-02-06) |
680 |:Fix Released: :rn:`5.6.11-60.3` |
681 |:Upstream fix: N/A |
682 +-------------------------------------------------------------------------------------------------------------+
683 |:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |
684 |:Launchpad bug: :bug:`800035` |
685-|:Upstream state: Verified (checked on 2015-01-12) |
686+|:Upstream state: Verified (checked on 2015-02-06) |
687 |:Fix Released: :rn:`5.6.11-60.3` |
688 |:Upstream fix: N/A |
689 +-------------------------------------------------------------------------------------------------------------+
690@@ -577,13 +583,13 @@
691 +-------------------------------------------------------------------------------------------------------------+
692 |:Upstream bug: :mysqlbug:`20001` - Support for temp-tables in INFORMATION_SCHEMA |
693 |:Launchpad bug: N/A |
694-|:Upstream state: Verified (checked on 2015-01-12) |
695+|:Upstream state: Verified (checked on 2015-02-06) |
696 |:Fix Released: :rn:`5.6.5-60.0` |
697 |:Upstream fix: N/A |
698 +-------------------------------------------------------------------------------------------------------------+
699 |:Upstream bug: :mysqlbug:`69146` - Optimization in buf_pool_get_oldest_modification if srv_buf_pool_instances|
700 |:Launchpad bug: :bug:`1176496` |
701-|:Upstream state: Verified (checked on 2015-01-12) |
702+|:Upstream state: Verified (checked on 2015-02-06) |
703 |:Fix Released: :rn:`5.6.5-60.0` |
704 |:Upstream fix: N/A |
705 +-------------------------------------------------------------------------------------------------------------+

Subscribers

People subscribed via source and target branches