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

Merge lp:~hrvojem/percona-server/rn-5.6.17-66.0-5.6 into lp:percona-server/5.6

  1. rn-5.6.17-66.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: 606
Proposed branch: lp:~hrvojem/percona-server/rn-5.6.17-66.0-5.6
Merge into: lp:percona-server/5.6
Diff against target: 724 lines (+332/-73)
9 files modified
doc/source/conf.py (+1/-1)
doc/source/index.rst (+2/-0)
doc/source/management/start_transaction_with_consistent_snapshot.rst (+64/-0)
doc/source/performance/handlersocket.rst (+106/-0)
doc/source/release-notes/Percona-Server-5.6.17-66.0.rst (+43/-0)
doc/source/release-notes/release-notes_index.rst (+1/-0)
doc/source/tokudb/tokudb_installation.rst (+70/-33)
doc/source/tokudb/tokudb_intro.rst (+5/-5)
doc/source/upstream-bug-fixes.rst (+40/-34)
To merge this branch: bzr merge lp:~hrvojem/percona-server/rn-5.6.17-66.0-5.6
Reviewer Review Type Date Requested Status
Laurynas Biveinis (community) Approve
Review via email: mp+222485@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) :
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 2014-05-30 13:32:03 +0000
3+++ doc/source/conf.py 2014-06-09 16:20:30 +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.17-65.0'
9+release = '5.6.17-66.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 2014-05-06 12:43:39 +0000
16+++ doc/source/index.rst 2014-06-09 16:20:30 +0000
17@@ -70,6 +70,7 @@
18 performance/atomic_fio
19 performance/query_cache_enhance
20 performance/innodb_numa_support
21+ performance/handlersocket
22 performance/buff_read_ahead_area
23 performance/threadpool
24 performance/page_cleaner_tuning
25@@ -125,6 +126,7 @@
26 management/statement_timeout
27 management/backup_locks
28 management/audit_log_plugin
29+ management/start_transaction_with_consistent_snapshot
30
31 Diagnostics Improvements
32 ========================
33
34=== added file 'doc/source/management/start_transaction_with_consistent_snapshot.rst'
35--- doc/source/management/start_transaction_with_consistent_snapshot.rst 1970-01-01 00:00:00 +0000
36+++ doc/source/management/start_transaction_with_consistent_snapshot.rst 2014-06-09 16:20:30 +0000
37@@ -0,0 +1,64 @@
38+.. _start_transaction_with_consistent_snapshot:
39+
40+============================================
41+ Start transaction with consistent snapshot
42+============================================
43+
44+|Percona Server|, in :rn:`5.6.17-66.0`, has ported *MariaDB* `enhancement <https://mariadb.com/kb/en/enhancements-for-start-transaction-with-consistent/>`_ for ``START TRANSACTION WITH CONSISTENT SNAPSHOTS`` feature to |MySQL| 5.6 group commit implementation. This enhancement makes binary log positions consistent with |InnoDB| transaction snapshots.
45+
46+This feature is quite useful to obtain logical backups with correct positions without running a ``FLUSH TABLES WITH READ LOCK``. Binary log position can be obtained by two newly implemented status variables: :variable:`Binlog_snapshot_file` and :variable:`Binlog_snapshot_position`. After starting a transaction using the ``START TRANSACTION WITH CONSISTENT SNAPSHOT``, these two variables will provide you with the binlog position corresponding to the state of the database of the consistent snapshot so taken, irrespectively of which other transactions have been committed since the snapshot was taken.
47+
48+.. _snapshot_cloning:
49+
50+Snapshot Cloning
51+================
52+
53+The |Percona Server| implementation extends the ``START TRANSACTION WITH CONSISTENT SNAPSHOT`` syntax with the optional ``FROM SESSION`` clause:
54+
55+.. code-block:: mysql
56+
57+ START TRANSACTION WITH CONSISTENT SNAPSHOT FROM SESSION <session_id>;
58+
59+When specified, all participating storage engines and binary log instead of creating a new snapshot of data (or binary log coordinates), create a copy of the snapshot which has been created by an active transaction in the specified session. ``session_id`` is the session identifier reported in the ``Id`` column of ``SHOW PROCESSLIST``.
60+
61+Currently snapshot cloning is only supported by |XtraDB| and the binary log. As with the regular ``START TRANSACTION WITH CONSISTENT SNAPSHOT``, snapshot clones can only be created with the ``REPEATABLE READ`` isolation level.
62+
63+For |XtraDB|, a transaction with a cloned snapshot will only see data visible or changed by the donor transaction. That is, the cloned transaction will see no changes committed by transactions that started after the donor transaction, not even changes made by itself. Note that in case of chained cloning the donor transaction is the first one in the chain. For example, if transaction A is cloned into transaction B, which is in turn cloned into transaction C, the latter will have read view from transaction A (i.e. the donor transaction). Therefore, it will see changes made by transaction A, but not by transaction B.
64+
65+mysqldump
66+=========
67+
68+``mysqldump`` has been updated to use new status variables automatically when they are supported by the server and both :option:`--single-transaction` and :option:`--master-data` are specified on the command line. Along with the ``mysqldump`` improvements introduced in :ref:`backup_locks` there is now a way to generate ``mysqldump`` backups that are guaranteed to be consistent without using ``FLUSH TABLES WITH READ LOCK`` even if :option:`--master-data` is requested.
69+
70+System Variables
71+================
72+
73+.. variable:: have_snapshot_cloning
74+
75+ :version 5.6.16-64.0: Implemented
76+ :cli: Yes
77+ :conf: No
78+ :scope: Global
79+ :dyn: No
80+ :vartype: Boolean
81+
82+This server variable is implemented to help other utilities detect if the server supports the ``FROM SESSION`` extension. When available, the snapshot cloning feature and the syntax extension to ``START TRANSACTION WITH CONSISTENT SNAPSHOT`` are supported by the server, and the variable value is always ``YES``.
83+
84+Status Variables
85+================
86+
87+.. variable:: Binlog_snapshot_file
88+
89+ :version 5.6.17-66.0: Implemented
90+ :vartype: Numeric
91+
92+.. variable:: Binlog_snapshot_position
93+
94+ :version 5.6.17-66.0: Implemented
95+ :vartype: Numeric
96+
97+These status variables are only available when the binary log is enabled globally.
98+
99+Other Reading
100+=============
101+* `MariaDB Enhancements for START TRANSACTION WITH CONSISTENT SNAPSHOT <https://mariadb.com/kb/en/enhancements-for-start-transaction-with-consistent/>`_
102
103=== added file 'doc/source/performance/handlersocket.rst'
104--- doc/source/performance/handlersocket.rst 1970-01-01 00:00:00 +0000
105+++ doc/source/performance/handlersocket.rst 2014-06-09 16:20:30 +0000
106@@ -0,0 +1,106 @@
107+.. _handlersocket_page:
108+
109+=================
110+ *HandlerSocket*
111+=================
112+
113+Description
114+===========
115+
116+*HandlerSocket* is a |MySQL| plugin that implements a ``NoSQL`` protocol for |MySQL|. This allows applications to communicate more directly with |MySQL| storage engines, without the overhead associated with using ``SQL``. This includes operations such as parsing and optimizing queries, as well as table handling operations (opening, locking, unlocking, closing). As a result, using *HandlerSocket* can provide much better performance for certain applications that using normal ``SQL`` application protocols.
117+
118+Complete documentation on the *HandlerSocket* plugin, including installation and configuration options, is located in the `project repository <https://github.com/DeNA/HandlerSocket-Plugin-for-MySQL>`_.
119+
120+The plugin is disabled by default. To enable it in |Percona Server| with |XtraDB|, see below.
121+
122+Version Specific Information
123+============================
124+
125+ * :rn:`5.6.17-66.0`
126+ Full functionality available.
127+
128+Other Information
129+
130+Author/Origin Akira Higuchi, DeNA Co., Ltd.
131+
132+Enabling the Plugin
133+===================
134+
135+Once *HandlerSocket* has been downloaded and installed on your system, there are two steps required to enable it.
136+
137+First, add the following lines to the [mysqld] section of your :term:`my.cnf` file: ::
138+
139+ loose_handlersocket_port = 9998
140+ # the port number to bind to for read requests
141+ loose_handlersocket_port_wr = 9999
142+ # the port number to bind to for write requests
143+ loose_handlersocket_threads = 16
144+ # the number of worker threads for read requests
145+ loose_handlersocket_threads_wr = 1
146+ # the number of worker threads for write requests
147+ open_files_limit = 65535
148+ # to allow handlersocket to accept many concurrent
149+ # connections, make open_files_limit as large as
150+ # possible.
151+
152+Second, log in to mysql as root, and execute the following query: ::
153+
154+ mysql> install plugin handlersocket soname 'handlersocket.so';
155+
156+Testing the Plugin installation
157+===============================
158+
159+If :file:`handlersocket.so` was successfully installed, it will begin accepting connections on ports 9998 and 9999. Executing a ``SHOW PROCESSLIST`` command should show *HandlerSocket* worker threads: ::
160+
161+ mysql> SHOW PROCESSLIST;
162+ +----+-------------+-----------------+---------------+---------+------+-------------------------------------------+------------------+
163+ | Id | User | Host | db | Command | Time | State | Info |
164+ +----+-------------+-----------------+---------------+---------+------+-------------------------------------------+------------------+
165+ | 1 | system user | connecting host | NULL | Connect | NULL | handlersocket: mode=rd, 0 conns, 0 active | NULL |
166+ | 2 | system user | connecting host | NULL | Connect | NULL | handlersocket: mode=rd, 0 conns, 0 active | NULL |
167+ ...
168+ | 16 | system user | connecting host | NULL | Connect | NULL | handlersocket: mode=rd, 0 conns, 0 active | NULL |
169+ | 17 | system user | connecting host | handlersocket | Connect | NULL | handlersocket: mode=wr, 0 conns, 0 active | NULL |
170+
171+To ensure *HandlerSocket* is working as expected, you can follow these steps:
172+
173+Create a new table: ::
174+
175+ mysql> CREATE TABLE t (
176+ id int(11) NOT NULL,
177+ col varchar(20) NOT NULL,
178+ PRIMARY KEY (id)
179+ ) ENGINE=InnoDB;
180+
181+Insert a row with *HandlerSocket* (fields are separated by comma): ::
182+
183+ $ telnet 127.0.0.1 9999
184+ Trying 127.0.0.1...
185+ Connected to 127.0.0.1.
186+ Escape character is '^]'.
187+ P 1 test t PRIMARY id,col
188+ 0 1
189+ 1 + 2 1 test value
190+ 0 1
191+
192+And check in SQL that the row has been written: ::
193+
194+ mysql> SELECT * FROM t;
195+ +----+------------+
196+ | id | col |
197+ +----+------------+
198+ | 1 | test value |
199+ +----+------------+
200+
201+Configuration options
202+---------------------
203+
204+*HandlerSocket* has many configuration options that are detailed `here <https://github.com/ahiguti/HandlerSocket-Plugin-for-MySQL/blob/master/docs-en/configuration-options.en.txt>`_.
205+
206+
207+Other Reading
208+=============
209+
210+ * Yoshinori Matsunobu's blog post describing `HandlerSocket <http://yoshinorimatsunobu.blogspot.com/2010/10/using-mysql-as-nosql-story-for.html>`_
211+
212+ * `Percona Server now both SQL and NOSQL <http://www.mysqlperformanceblog.com/2010/12/14/percona-server-now-both-sql-and-nosql/>`_
213
214=== added file 'doc/source/release-notes/Percona-Server-5.6.17-66.0.rst'
215--- doc/source/release-notes/Percona-Server-5.6.17-66.0.rst 1970-01-01 00:00:00 +0000
216+++ doc/source/release-notes/Percona-Server-5.6.17-66.0.rst 2014-06-09 16:20:30 +0000
217@@ -0,0 +1,43 @@
218+.. rn:: 5.6.17-66.0
219+
220+==============================
221+ |Percona Server| 5.6.17-66.0
222+==============================
223+
224+Percona is glad to announce the release of |Percona Server| 5.6.17-66.0 on June 11th, 2014 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.17-66.0/>`_ and from the :doc:`Percona Software Repositories </installation>`).
225+
226+Based on `MySQL 5.6.17 <http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-17.html>`_, including all the bug fixes in it, |Percona Server| 5.6.17-66.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.17-66.0 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.6.17-66.0>`_.
227+
228+New Features
229+============
230+
231+ |MySQL| benchmarks (``sql-bench`` directory in the |MySQL| distribution) has been made compatible with the TokuDB storage engine.
232+
233+ |Percona Server| has ported *MariaDB* code enhancement for :ref:`start transaction with consistent snapshot <start_transaction_with_consistent_snapshot>`. This enhancement makes binary log positions consistent with |InnoDB| transaction snapshots.
234+
235+ |Percona Server| has implemented ability to :ref:`clone a snapshot <snapshot_cloning>` created by ``START TRANSACTION WITH CONSISTENT SNAPSHOT`` in another session.
236+
237+ TokuDB Storage engine is now available as a separate package that can be :ref:`installed <tokudb_installation>` along with the |Percona Server| 5.6.17-66.0. This feature is currently considered Release Candidate quality.
238+
239+ |Percona Server| version 5.6 now includes :ref:`handlersocket_page` in addition to 5.5.
240+
241+Bugs Fixed
242+==========
243+
244+ Fix for :bug:`1225189` introduced a regression in |Percona Server| :rn:`5.6.13-61.0` which could lead to an error when running ``mysql_install_db``. Bug fixed :bug:`1314596`.
245+
246+ |InnoDB| could crash if workload contained writes to compressed tables. Bug fixed :bug:`1305364`.
247+
248+ GUI clients such as *MySQL Workbench* could not authenticate with a user defined with ``auth_pam_compat`` plugin. Bug fixed :bug:`1166938`.
249+
250+ Help in |Percona Server| 5.6 command line client was linking to |Percona Server| 5.1 manual. Bug fixed :bug:`1198775`.
251+
252+ |InnoDB| redo log resizing could crash when :ref:`changed_page_tracking` was enabled. Bug fixed :bug:`1204072`.
253+
254+ :ref:`audit_log_plugin` wasn't parsing escape characters correctly in the ``OLD`` format. Bug fixed :bug:`1313696`.
255+
256+ |Percona Server| version was reported incorrectly in *Debian*/*Ubuntu* packages. Bug fixed :bug:`1319670`.
257+
258+Other bugs fixed: :bug:`1318537` (upstream :mysqlbug:`72615`), :bug:`1318874`, :bug:`1285618`, :bug:`1272732`, :bug:`1314568`, :bug:`1271178`, and :bug:`1323014`.
259+
260+
261
262=== modified file 'doc/source/release-notes/release-notes_index.rst'
263--- doc/source/release-notes/release-notes_index.rst 2014-05-30 13:32:03 +0000
264+++ doc/source/release-notes/release-notes_index.rst 2014-06-09 16:20:30 +0000
265@@ -6,6 +6,7 @@
266 :maxdepth: 1
267 :glob:
268
269+ Percona-Server-5.6.17-66.0
270 Percona-Server-5.6.17-65.0
271 Percona-Server-5.6.16-64.2-tokudb
272 Percona-Server-5.6.16-64.2
273
274=== modified file 'doc/source/tokudb/tokudb_installation.rst'
275--- doc/source/tokudb/tokudb_installation.rst 2014-03-27 07:04:17 +0000
276+++ doc/source/tokudb/tokudb_installation.rst 2014-06-09 16:20:30 +0000
277@@ -4,20 +4,48 @@
278 TokuDB Installation
279 =====================
280
281-.. warning::
282-
283- This feature is considered **BETA** quality and it isn't recommended for production use.
284-
285-|Percona Server| has added support for TokuDB storage engine in the :rn:`5.6.16-64.0-tokudb` release.
286+.. note::
287+
288+ This feature is considered **RELEASE CANDIDATE** quality and it isn't recommended for production use.
289+
290+|Percona Server| has added support for TokuDB storage engine in the :rn:`5.6.16-64.0-tokudb` release, and TokuDB storage engine is available as a separate package from :rn:`5.6.17-66.0` release.
291
292 `TokuDB <http://www.tokutek.com/products/tokudb-for-mysql/>`_ is a scalable, ACID and MVCC compliant storage engine that provides indexing-based query improvements, offers online schema modifications, and reduces slave lag for both hard disk drives and flash memory. This storage engine is specifically designed for high performance on write-intensive workloads which is achieved with Fractal Tree indexing.
293
294 TokuDB is currently supported only for 64-bit Linux distributions.
295
296+Prerequisites
297+=============
298+
299+``libjemalloc`` library
300+-----------------------
301+
302+TokuDB storage engine requires ``libjemalloc`` library 3.3.0 or greater. If the version in the distribution repository is lower than that you can use one from :ref:`Percona Software Repositories <installation>` or download it from somewhere else.
303+
304+If the ``libjemalloc`` wasn't installed and enabled before it will be automatically installed when installing the TokuDB storage engine package by using the ``apt`` or ``yum`` package manager, but |Percona Server| instance should be restarted for ``libjemalloc`` to be loaded. This way ``libjemalloc`` will be loaded with ``LD_PRELOAD``. You can also enable ``libjemalloc`` by specifying :variable:`malloc-lib` variable in the ``[mysqld_safe]`` section of the :file:`my.cnf` file: ::
305+
306+ [mysqld_safe]
307+ malloc-lib= /path/to/jemalloc
308+
309+
310+Transparent huge pages
311+----------------------
312+
313+TokuDB won't be able to start if the transparent huge pages are enabled. `Transparent huge pages <https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Performance_Tuning_Guide/s-memory-transhuge.html>`_ is feature available in the newer kernel versions. You can check if the Transparent huge pages are enabled with: ::
314+
315+ $ cat /sys/kernel/mm/transparent_hugepage/enabled
316+
317+ [always] madvise never
318+
319+ You can `disable <http://www.oracle-base.com/articles/linux/configuring-huge-pages-for-oracle-on-linux-64.php#disabling-transparent-hugepages>`_ them by passing ``transparent_hugepage=never`` to the kernel in your bootloader or by running: ::
320+
321+ $ echo never > /sys/kernel/mm/transparent_hugepage/enabled
322+ $ echo never > /sys/kernel/mm/transparent_hugepage/defrag
323+
324 Installation
325 ============
326
327-|Percona Server| with TokuDB is currently available in our :ref:`apt experimental <apt_repo>` and :ref:`yum testing <yum_repo>` repositories.
328+TokuDB storage engine for |Percona Server| is currently available in our :ref:`apt <apt_repo>` and :ref:`yum <yum_repo>` repositories.
329
330 You can install the |Percona Server| with TokuDB engine by using the apt/yum commands:
331
332@@ -25,38 +53,17 @@
333
334 [root@centos ~]# yum install Percona-Server-tokudb-56.x86_64
335
336-or
337+or
338
339 .. code-block:: bash
340
341 root@wheezy:~# apt-get install percona-server-tokudb-5.6
342
343-.. note::
344-
345- TokuDB won't be able to start if the transparent huge pages are enabled. `Transparent huge pages <https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Performance_Tuning_Guide/s-memory-transhuge.html>`_ is feature available in the newer kernel versions. You can check if the Transparent huge pages are enabled with: ::
346-
347- $ cat /sys/kernel/mm/transparent_hugepage/enabled
348-
349- [always] madvise never
350-
351- You can `disable <http://www.oracle-base.com/articles/linux/configuring-huge-pages-for-oracle-on-linux-64.php#disabling-transparent-hugepages>`_ them by passing ``transparent_hugepage=never`` to the kernel in your bootloader or by running: ::
352-
353- $ echo never > /sys/kernel/mm/transparent_hugepage/enabled
354- $ echo never > /sys/kernel/mm/transparent_hugepage/defrag
355-
356-
357-Upgrade
358-=======
359-
360-Upgrading from other |Percona Server| 5.5 and 5.6 releases should work without problems (you should read :ref:`changed_in_56` before upgrading from |Percona Server| 5.5 to |Percona Server| 5.6 with TokuDB engine).
361-
362-
363-Manually enabling the TokuDB support
364-====================================
365-
366-After |Percona Server| :rn:`5.6.16-64.2-tokudb` release, TokuDB engine will be automatically enabled during new installations.
367-
368-This plugin will require manual installation if there is a root password already set up during the new installation or upgrade.
369+
370+Enabling the TokuDB Storage Engine
371+==================================
372+
373+This storage engine requires manual installation if there is a root password already set up during the new installation or upgrade.
374
375 .. code-block:: mysql
376
377@@ -92,6 +99,36 @@
378 | TokuDB_lock_waits | ACTIVE | INFORMATION SCHEMA | ha_tokudb.so | GPL |
379 ...
380
381+TokuDB Version
382+==============
383+
384+TokuDB storage engine version can be checked with:
385+
386+.. code-block:: mysql
387+
388+ mysql> SELECT @@tokudb_version;
389+ +------------------+
390+ | @@tokudb_version |
391+ +------------------+
392+ | tokudb-7.1.7-rc7 |
393+ +------------------+
394+ 1 row in set (0.00 sec)
395+
396+
397+Upgrade
398+=======
399+
400+Installing the TokuDB package is compatible with existing server setup and databases.
401+
402+Version Specific Information
403+============================
404+
405+ * :rn:`5.6.16-64.0-tokudb`
406+ TokuDB Storage engine available in special |Percona Server| release.
407+ * :rn:`5.6.17-66.0`
408+ TokuDB storage engine available as a separate |Percona Server| package.
409+
410+
411 Other Reading
412 =============
413
414
415=== modified file 'doc/source/tokudb/tokudb_intro.rst'
416--- doc/source/tokudb/tokudb_intro.rst 2014-03-27 07:04:17 +0000
417+++ doc/source/tokudb/tokudb_intro.rst 2014-06-09 16:20:30 +0000
418@@ -4,11 +4,11 @@
419 TokuDB Introduction
420 =====================
421
422-.. warning::
423-
424- This feature is considered **BETA** quality and it isn't recommended for production use.
425-
426-|Percona Server| has added support for TokuDB storage engine in the :rn:`5.6.16-64.0-tokudb` release. TokuDB engine is only available in special |Percona Server| with TokuDB storage engine releases.
427+.. note::
428+
429+ This feature is considered **RELEASE CANDIDATE** quality and it isn't recommended for production use.
430+
431+|Percona Server| provides the separate TokuDB storage engine package since :rn:`5.6.17-66.0`. This package can be :ref:`installed <tokudb_installation>` along side with |Percona Server| 5.6 releases. Before the separate package implementation |Percona Server| has added support for TokuDB storage engine in the :rn:`5.6.16-64.0-tokudb` release and TokuDB engine was only available in special |Percona Server| with TokuDB storage engine releases.
432
433 TokuDB is a scalable, ACID and MVCC compliant storage engine that provides indexing-based query improvements, offers online schema modifications, and reduces slave lag for both hard disk drives and flash memory. This storage engine is specifically designed for high performance on write-intensive workloads which is achieved with Fractal Tree indexing.
434
435
436=== modified file 'doc/source/upstream-bug-fixes.rst'
437--- doc/source/upstream-bug-fixes.rst 2014-06-04 15:01:17 +0000
438+++ doc/source/upstream-bug-fixes.rst 2014-06-09 16:20:30 +0000
439@@ -5,15 +5,21 @@
440 =============================================================
441
442 +-------------------------------------------------------------------------------------------------------------+
443+|:Upstream bug: :mysqlbug:`72615` - MTR --mysqld=--default-storage-engine=foo incompatible w/ dynamically... |
444+|:Launchpad bug: :bug:`1318537` |
445+|:Upstream state: Verified (checked on 2014-06-09) |
446+|:Fix Released: :rn:`5.6.17-66.0` |
447+|:Upstream fix: N/A |
448++-------------------------------------------------------------------------------------------------------------+
449 |:Upstream bug: :mysqlbug:`72163` - Rev 5774 broke rpl_plugin_load |
450 |:Launchpad bug: :bug:`1299688` |
451-|:Upstream state: Verified (checked on 2014-04-30) |
452+|:Upstream state: Verified (checked on 2014-06-09) |
453 |:Fix Released: :rn:`5.6.17-65.0` |
454 |:Upstream fix: N/A |
455 +-------------------------------------------------------------------------------------------------------------+
456 |:Upstream bug: :mysqlbug:`60782` - Audit plugin API: no MYSQL_AUDIT_GENERAL_LOG notifications with general...|
457 |:Launchpad bug: :bug:`1182535` |
458-|:Upstream state: Verified (checked on 2014-04-30) |
459+|:Upstream state: Verified (checked on 2014-06-09) |
460 |:Fix Released: :rn:`5.6.17-65.0` |
461 |:Upstream fix: N/A |
462 +-------------------------------------------------------------------------------------------------------------+
463@@ -25,19 +31,19 @@
464 +-------------------------------------------------------------------------------------------------------------+
465 |:Upstream bug: :mysqlbug:`71374` - Slave IO thread won't attempt auto reconnect to the master/error-code 1159|
466 |:Launchpad bug: :bug:`1268729` |
467-|:Upstream state: Verified (checked on 2014-04-30) |
468+|:Upstream state: Verified (checked on 2014-06-09) |
469 |:Fix Released: :rn:`5.6.16-64.1` |
470 |:Upstream fix: N/A |
471 +-------------------------------------------------------------------------------------------------------------+
472 |:Upstream bug: :mysqlbug:`71988` - page_cleaner: aggressive background flushing |
473 |:Launchpad bug: :bug:`1238039` |
474-|:Upstream state: Verified (checked on 2014-04-30) |
475+|:Upstream state: Verified (checked on 2014-06-09) |
476 |:Fix Released: :rn:`5.6.16-64.0` |
477 |:Upstream fix: N/A |
478 +-------------------------------------------------------------------------------------------------------------+
479 |:Upstream bug: :mysqlbug:`71624` - printf size_t results in a fatal warning in 32-bit debug builds |
480 |:Launchpad bug: :bug:`1277505` |
481-|:Upstream state: Can't repeat (checked on 2014-04-30) |
482+|:Upstream state: Can't repeat (checked on 2014-06-09) |
483 |:Fix Released: :rn:`5.6.16-64.0` |
484 |:Upstream fix: N/A |
485 +-------------------------------------------------------------------------------------------------------------+
486@@ -79,13 +85,13 @@
487 +-------------------------------------------------------------------------------------------------------------+
488 |:Upstream bug: :mysqlbug:`71270` - Failures to end bulk insert for partitioned tables handled incorrectly |
489 |:Launchpad bug: :bug:`1204871` |
490-|:Upstream state: Verified (checked on 2014-04-30) |
491+|:Upstream state: Verified (checked on 2014-06-09) |
492 |:Fix Released: :rn:`5.6.16-64.0` |
493 |:Upstream fix: N/A |
494 +-------------------------------------------------------------------------------------------------------------+
495 |:Upstream bug: :mysqlbug:`71217` - Threadpool - add thd_wait_begin/thd_wait_end to the network IO functions |
496 |:Launchpad bug: :bug:`1159743` |
497-|:Upstream state: Open (checked on 2014-04-30) |
498+|:Upstream state: Open (checked on 2014-06-09) |
499 |:Fix Released: :rn:`5.6.15-63.0` |
500 |:Upstream fix: N/A |
501 +-------------------------------------------------------------------------------------------------------------+
502@@ -103,7 +109,7 @@
503 +-------------------------------------------------------------------------------------------------------------+
504 |:Upstream bug: :mysqlbug:`71411` - buf_flush_LRU() does not return correct number in case of compressed pages|
505 |:Launchpad bug: :bug:`1231918` |
506-|:Upstream state: Verified (checked on 2014-04-30) |
507+|:Upstream state: Verified (checked on 2014-06-09) |
508 |:Fix Released: :rn:`5.6.13-61.0` |
509 |:Upstream fix: N/A |
510 +-------------------------------------------------------------------------------------------------------------+
511@@ -115,7 +121,7 @@
512 +-------------------------------------------------------------------------------------------------------------+
513 |:Upstream bug: :mysqlbug:`70490` - Suppression is too strict on some systems |
514 |:Launchpad bug: :bug:`1205196` |
515-|:Upstream state: No Feedback (checked on 2014-04-30) |
516+|:Upstream state: No Feedback (checked on 2014-06-09) |
517 |:Fix Released: :rn:`5.6.13-61.0` |
518 |:Upstream fix: N/A |
519 +-------------------------------------------------------------------------------------------------------------+
520@@ -127,7 +133,7 @@
521 +-------------------------------------------------------------------------------------------------------------+
522 |:Upstream bug: :mysqlbug:`70500` - Page cleaner should perform LRU flushing regardless of server activity |
523 |:Launchpad bug: :bug:`1234562` |
524-|:Upstream state: Open (checked on 2014-04-30) |
525+|:Upstream state: Open (checked on 2014-06-09) |
526 |:Fix Released: :rn:`5.6.13-61.0` |
527 |:Upstream fix: N/A |
528 +-------------------------------------------------------------------------------------------------------------+
529@@ -145,31 +151,31 @@
530 +-------------------------------------------------------------------------------------------------------------+
531 |:Upstream bug: :mysqlbug:`68481` - InnoDB LRU flushing for MySQL 5.6 needs work |
532 |:Launchpad bug: :bug:`1232406` |
533-|:Upstream state: Verified (checked on 2014-04-30) |
534+|:Upstream state: Verified (checked on 2014-06-09) |
535 |:Fix Released: :rn:`5.6.13-61.0` |
536 |:Upstream fix: N/A |
537 +-------------------------------------------------------------------------------------------------------------+
538 |:Upstream bug: :mysqlbug:`70453` - Add hard timeouts to page cleaner flushes |
539 |:Launchpad bug: :bug:`1232101` |
540-|:Upstream state: Verified (checked on 2014-04-30) |
541+|:Upstream state: Verified (checked on 2014-06-09) |
542 |:Fix Released: :rn:`5.6.13-61.0` |
543 |:Upstream fix: N/A |
544 +-------------------------------------------------------------------------------------------------------------+
545 |:Upstream bug: :mysqlbug:`69170` - buf_flush_LRU is lazy |
546 |:Launchpad bug: :bug:`1231918` |
547-|:Upstream state: Verified (checked on 2014-04-30) |
548+|:Upstream state: Verified (checked on 2014-06-09) |
549 |:Fix Released: :rn:`5.6.13-61.0` |
550 |:Upstream fix: N/A |
551 +-------------------------------------------------------------------------------------------------------------+
552 |:Upstream bug: :mysqlbug:`68555` - thread convoys from log_checkpoint_margin with innodb_buffer_pool_inst... |
553 |:Launchpad bug: :bug:`1236884` |
554-|:Upstream state: Verified (checked on 2014-04-30) |
555+|:Upstream state: Verified (checked on 2014-06-09) |
556 |:Fix Released: :rn:`5.6.13-61.0` |
557 |:Upstream fix: N/A |
558 +-------------------------------------------------------------------------------------------------------------+
559 |:Upstream bug: :mysqlbug:`70228` - Is buf_LRU_free_page() really supposed to make non-zip block sticky at ...|
560 |:Launchpad bug: :bug:`1220544` |
561-|:Upstream state: Verified (checked on 2014-04-30) |
562+|:Upstream state: Verified (checked on 2014-06-09) |
563 |:Fix Released: :rn:`5.6.13-60.6` |
564 |:Upstream fix: N/A |
565 +-------------------------------------------------------------------------------------------------------------+
566@@ -187,13 +193,13 @@
567 +-------------------------------------------------------------------------------------------------------------+
568 |:Upstream bug: :mysqlbug:`70216` - Unnecessary overhead from persistent adaptive hash index latches |
569 |:Launchpad bug: :bug:`1218347` |
570-|:Upstream state: Verified (checked on 2014-04-30) |
571+|:Upstream state: Verified (checked on 2014-06-09) |
572 |:Fix Released: :rn:`5.6.13-60.6` |
573 |:Upstream fix: N/A |
574 +-------------------------------------------------------------------------------------------------------------+
575 |:Upstream bug: :mysqlbug:`62018` - innodb adaptive hash index mutex contention |
576 |:Launchpad bug: :bug:`1216804` |
577-|:Upstream state: Verified (checked on 2014-04-30) |
578+|:Upstream state: Verified (checked on 2014-06-09) |
579 |:Fix Released: :rn:`5.6.13-60.6` |
580 |:Upstream fix: N/A |
581 +-------------------------------------------------------------------------------------------------------------+
582@@ -211,13 +217,13 @@
583 +-------------------------------------------------------------------------------------------------------------+
584 |:Upstream bug: :mysqlbug:`42415` - UPDATE/DELETE with LIMIT clause unsafe for SBL even with ORDER BY PK ... |
585 |:Launchpad bug: :bug:`1132194` |
586-|:Upstream state: Verified (checked on 2014-04-30) |
587+|:Upstream state: Verified (checked on 2014-06-09) |
588 |:Fix Released: :rn:`5.6.13-60.5` |
589 |:Upstream fix: N/A |
590 +-------------------------------------------------------------------------------------------------------------+
591 |:Upstream bug: :mysqlbug:`69639` - mysql failed to build with dtrace Sun D 1.11 |
592 |:Launchpad bug: :bug:`1196460` |
593-|:Upstream state: Open (checked on 2014-04-30) |
594+|:Upstream state: Open (checked on 2014-06-09) |
595 |:Fix Released: :rn:`5.6.13-60.5` |
596 |:Upstream fix: N/A |
597 +-------------------------------------------------------------------------------------------------------------+
598@@ -235,7 +241,7 @@
599 +-------------------------------------------------------------------------------------------------------------+
600 |:Upstream bug: :mysqlbug:`69856` - mysql_install_db does not function properly in 5.6 for debug builds |
601 |:Launchpad bug: :bug:`1179359` |
602-|:Upstream state: Verified (checked on 2014-04-30) |
603+|:Upstream state: Verified (checked on 2014-06-09) |
604 |:Fix Released: :rn:`5.6.12-60.4` |
605 |:Upstream fix: N/A |
606 +-------------------------------------------------------------------------------------------------------------+
607@@ -247,7 +253,7 @@
608 +-------------------------------------------------------------------------------------------------------------+
609 |:Upstream bug: :mysqlbug:`71183` - os_file_fsync() should handle fsync() returning EINTR |
610 |:Launchpad bug: :bug:`1262651` |
611-|:Upstream state: Verified (checked on 2014-04-30) |
612+|:Upstream state: Verified (checked on 2014-06-09) |
613 |:Fix Released: :rn:`5.6.11-60.3` |
614 |:Upstream fix: N/A |
615 +-------------------------------------------------------------------------------------------------------------+
616@@ -277,7 +283,7 @@
617 +-------------------------------------------------------------------------------------------------------------+
618 |:Upstream bug: :mysqlbug:`68714` - Remove literal statement digest values from perfschema tests |
619 |:Launchpad bug: :bug:`1157078` |
620-|:Upstream state: Verified (checked on 2014-04-30) |
621+|:Upstream state: Verified (checked on 2014-06-09) |
622 |:Fix Released: :rn:`5.6.11-60.3` |
623 |:Upstream fix: N/A |
624 +-------------------------------------------------------------------------------------------------------------+
625@@ -301,13 +307,13 @@
626 +-------------------------------------------------------------------------------------------------------------+
627 |:Upstream bug: :mysqlbug:`68970` - fsp_reserve_free_extents switches from small to big tblspace handling ... |
628 |:Launchpad bug: :bug:`1169494` |
629-|:Upstream state: Verified (checked on 2014-04-30) |
630+|:Upstream state: Verified (checked on 2014-06-09) |
631 |:Fix Released: :rn:`5.6.11-60.3` |
632 |:Upstream fix: N/A |
633 +-------------------------------------------------------------------------------------------------------------+
634 |:Upstream bug: :mysqlbug:`68713` - create_duplicate_weedout_tmp_table() leaves key_part_flag uninitialized |
635 |:Launchpad bug: :bug:`1157037` |
636-|:Upstream state: Verified (checked on 2014-04-30) |
637+|:Upstream state: Verified (checked on 2014-06-09) |
638 |:Fix Released: :rn:`5.6.11-60.3` |
639 |:Upstream fix: N/A |
640 +-------------------------------------------------------------------------------------------------------------+
641@@ -319,13 +325,13 @@
642 +-------------------------------------------------------------------------------------------------------------+
643 |:Upstream bug: :mysqlbug:`68999` - SSL_OP_NO_COMPRESSION not defined |
644 |:Launchpad bug: :bug:`1183610` |
645-|:Upstream state: No Feedback (checked on 2014-04-30) |
646+|:Upstream state: No Feedback (checked on 2014-06-09) |
647 |:Fix Released: :rn:`5.6.11-60.3` |
648 |:Upstream fix: N/A |
649 +-------------------------------------------------------------------------------------------------------------+
650 |:Upstream bug: :mysqlbug:`68845` - Unnecessary log_sys->mutex reacquisition in mtr_log_reserve_and_write() |
651 |:Launchpad bug: :bug:`1163439` |
652-|:Upstream state: Verified (checked on 2014-04-30) |
653+|:Upstream state: Verified (checked on 2014-06-09) |
654 |:Fix Released: :rn:`5.6.11-60.3` |
655 |:Upstream fix: N/A |
656 +-------------------------------------------------------------------------------------------------------------+
657@@ -355,7 +361,7 @@
658 +-------------------------------------------------------------------------------------------------------------+
659 |:Upstream bug: :mysqlbug:`68476` - Suboptimal code in my_strnxfrm_simple() |
660 |:Launchpad bug: :bug:`1132350` |
661-|:Upstream state: Verified (checked on 2014-04-30) |
662+|:Upstream state: Verified (checked on 2014-06-09) |
663 |:Fix Released: :rn:`5.6.11-60.3` |
664 |:Upstream fix: N/A |
665 +-------------------------------------------------------------------------------------------------------------+
666@@ -415,7 +421,7 @@
667 +-------------------------------------------------------------------------------------------------------------+
668 |:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|
669 |:Launchpad bug: :bug:`1042517` |
670-|:Upstream state: Verified (checked on 2014-04-30) |
671+|:Upstream state: Verified (checked on 2014-06-09) |
672 |:Fix Released: :rn:`5.6.11-60.3` |
673 |:Upstream fix: N/A |
674 +-------------------------------------------------------------------------------------------------------------+
675@@ -427,7 +433,7 @@
676 +-------------------------------------------------------------------------------------------------------------+
677 |:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no. |
678 |:Launchpad bug: :bug:`1013432` |
679-|:Upstream state: Verified (checked on 2014-04-30) |
680+|:Upstream state: Verified (checked on 2014-06-09) |
681 |:Fix Released: :rn:`5.6.11-60.3` |
682 |:Upstream fix: N/A |
683 +-------------------------------------------------------------------------------------------------------------+
684@@ -457,13 +463,13 @@
685 +-------------------------------------------------------------------------------------------------------------+
686 |:Upstream bug: :mysqlbug:`25007` - memory tables with dynamic rows format |
687 |:Launchpad bug: N/A |
688-|:Upstream state: Verified (checked on 2014-04-30) |
689+|:Upstream state: Verified (checked on 2014-06-09) |
690 |:Fix Released: :rn:`5.6.11-60.3` |
691 |:Upstream fix: N/A |
692 +-------------------------------------------------------------------------------------------------------------+
693 |:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |
694 |:Launchpad bug: :bug:`800035` |
695-|:Upstream state: Verified (checked on 2014-04-30) |
696+|:Upstream state: Verified (checked on 2014-06-09) |
697 |:Fix Released: :rn:`5.6.11-60.3` |
698 |:Upstream fix: N/A |
699 +-------------------------------------------------------------------------------------------------------------+
700@@ -475,7 +481,7 @@
701 +-------------------------------------------------------------------------------------------------------------+
702 |:Upstream bug: :mysqlbug:`68116` - InnoDB monitor may hit an assertion error in buf_page_get_gen in debug ...|
703 |:Launchpad bug: :bug:`1100178` |
704-|:Upstream state: Verified (checked on 2014-04-30) |
705+|:Upstream state: Verified (checked on 2014-06-09) |
706 |:Fix Released: :rn:`5.6.10-60.2` |
707 |:Upstream fix: N/A |
708 +-------------------------------------------------------------------------------------------------------------+
709@@ -487,13 +493,13 @@
710 +-------------------------------------------------------------------------------------------------------------+
711 |:Upstream bug: :mysqlbug:`20001` - Support for temp-tables in INFORMATION_SCHEMA |
712 |:Launchpad bug: N/A |
713-|:Upstream state: Verified (checked on 2014-04-30) |
714+|:Upstream state: Verified (checked on 2014-06-09) |
715 |:Fix Released: :rn:`5.6.5-60.0` |
716 |:Upstream fix: N/A |
717 +-------------------------------------------------------------------------------------------------------------+
718 |:Upstream bug: :mysqlbug:`69146` - Optimization in buf_pool_get_oldest_modification if srv_buf_pool_instances|
719 |:Launchpad bug: :bug:`1176496` |
720-|:Upstream state: Open (checked on 2014-04-30) |
721+|:Upstream state: Verified (checked on 2014-06-09) |
722 |:Fix Released: :rn:`5.6.5-60.0` |
723 |:Upstream fix: N/A |
724 +-------------------------------------------------------------------------------------------------------------+

Subscribers

People subscribed via source and target branches