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

Proposed by Hrvoje Matijakovic on 2014-06-09
Status: Merged
Approved by: Laurynas Biveinis on 2014-06-09
Approved revision: 605
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) 2014-06-09 Approve on 2014-06-09
Review via email: mp+222485@code.launchpad.net
To post a comment you must log in.
review: Needs Fixing
review: Needs Fixing
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== modified file 'doc/source/conf.py'
--- doc/source/conf.py 2014-05-30 13:32:03 +0000
+++ doc/source/conf.py 2014-06-09 16:20:30 +0000
@@ -54,7 +54,7 @@
54# The short X.Y version.54# The short X.Y version.
55version = '5.6'55version = '5.6'
56# The full version, including alpha/beta/rc tags.56# The full version, including alpha/beta/rc tags.
57release = '5.6.17-65.0'57release = '5.6.17-66.0'
5858
59# The language for content autogenerated by Sphinx. Refer to documentation59# The language for content autogenerated by Sphinx. Refer to documentation
60# for a list of supported languages.60# for a list of supported languages.
6161
=== modified file 'doc/source/index.rst'
--- doc/source/index.rst 2014-05-06 12:43:39 +0000
+++ doc/source/index.rst 2014-06-09 16:20:30 +0000
@@ -70,6 +70,7 @@
70 performance/atomic_fio70 performance/atomic_fio
71 performance/query_cache_enhance71 performance/query_cache_enhance
72 performance/innodb_numa_support72 performance/innodb_numa_support
73 performance/handlersocket
73 performance/buff_read_ahead_area74 performance/buff_read_ahead_area
74 performance/threadpool75 performance/threadpool
75 performance/page_cleaner_tuning76 performance/page_cleaner_tuning
@@ -125,6 +126,7 @@
125 management/statement_timeout126 management/statement_timeout
126 management/backup_locks127 management/backup_locks
127 management/audit_log_plugin128 management/audit_log_plugin
129 management/start_transaction_with_consistent_snapshot
128130
129Diagnostics Improvements131Diagnostics Improvements
130========================132========================
131133
=== added file 'doc/source/management/start_transaction_with_consistent_snapshot.rst'
--- doc/source/management/start_transaction_with_consistent_snapshot.rst 1970-01-01 00:00:00 +0000
+++ doc/source/management/start_transaction_with_consistent_snapshot.rst 2014-06-09 16:20:30 +0000
@@ -0,0 +1,64 @@
1.. _start_transaction_with_consistent_snapshot:
2
3============================================
4 Start transaction with consistent snapshot
5============================================
6
7|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.
8
9This 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.
10
11.. _snapshot_cloning:
12
13Snapshot Cloning
14================
15
16The |Percona Server| implementation extends the ``START TRANSACTION WITH CONSISTENT SNAPSHOT`` syntax with the optional ``FROM SESSION`` clause:
17
18.. code-block:: mysql
19
20 START TRANSACTION WITH CONSISTENT SNAPSHOT FROM SESSION <session_id>;
21
22When 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``.
23
24Currently 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.
25
26For |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.
27
28mysqldump
29=========
30
31``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.
32
33System Variables
34================
35
36.. variable:: have_snapshot_cloning
37
38 :version 5.6.16-64.0: Implemented
39 :cli: Yes
40 :conf: No
41 :scope: Global
42 :dyn: No
43 :vartype: Boolean
44
45This 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``.
46
47Status Variables
48================
49
50.. variable:: Binlog_snapshot_file
51
52 :version 5.6.17-66.0: Implemented
53 :vartype: Numeric
54
55.. variable:: Binlog_snapshot_position
56
57 :version 5.6.17-66.0: Implemented
58 :vartype: Numeric
59
60These status variables are only available when the binary log is enabled globally.
61
62Other Reading
63=============
64* `MariaDB Enhancements for START TRANSACTION WITH CONSISTENT SNAPSHOT <https://mariadb.com/kb/en/enhancements-for-start-transaction-with-consistent/>`_
065
=== added file 'doc/source/performance/handlersocket.rst'
--- doc/source/performance/handlersocket.rst 1970-01-01 00:00:00 +0000
+++ doc/source/performance/handlersocket.rst 2014-06-09 16:20:30 +0000
@@ -0,0 +1,106 @@
1.. _handlersocket_page:
2
3=================
4 *HandlerSocket*
5=================
6
7Description
8===========
9
10*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.
11
12Complete documentation on the *HandlerSocket* plugin, including installation and configuration options, is located in the `project repository <https://github.com/DeNA/HandlerSocket-Plugin-for-MySQL>`_.
13
14The plugin is disabled by default. To enable it in |Percona Server| with |XtraDB|, see below.
15
16Version Specific Information
17============================
18
19 * :rn:`5.6.17-66.0`
20 Full functionality available.
21
22Other Information
23
24Author/Origin Akira Higuchi, DeNA Co., Ltd.
25
26Enabling the Plugin
27===================
28
29Once *HandlerSocket* has been downloaded and installed on your system, there are two steps required to enable it.
30
31First, add the following lines to the [mysqld] section of your :term:`my.cnf` file: ::
32
33 loose_handlersocket_port = 9998
34 # the port number to bind to for read requests
35 loose_handlersocket_port_wr = 9999
36 # the port number to bind to for write requests
37 loose_handlersocket_threads = 16
38 # the number of worker threads for read requests
39 loose_handlersocket_threads_wr = 1
40 # the number of worker threads for write requests
41 open_files_limit = 65535
42 # to allow handlersocket to accept many concurrent
43 # connections, make open_files_limit as large as
44 # possible.
45
46Second, log in to mysql as root, and execute the following query: ::
47
48 mysql> install plugin handlersocket soname 'handlersocket.so';
49
50Testing the Plugin installation
51===============================
52
53If :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: ::
54
55 mysql> SHOW PROCESSLIST;
56 +----+-------------+-----------------+---------------+---------+------+-------------------------------------------+------------------+
57 | Id | User | Host | db | Command | Time | State | Info |
58 +----+-------------+-----------------+---------------+---------+------+-------------------------------------------+------------------+
59 | 1 | system user | connecting host | NULL | Connect | NULL | handlersocket: mode=rd, 0 conns, 0 active | NULL |
60 | 2 | system user | connecting host | NULL | Connect | NULL | handlersocket: mode=rd, 0 conns, 0 active | NULL |
61 ...
62 | 16 | system user | connecting host | NULL | Connect | NULL | handlersocket: mode=rd, 0 conns, 0 active | NULL |
63 | 17 | system user | connecting host | handlersocket | Connect | NULL | handlersocket: mode=wr, 0 conns, 0 active | NULL |
64
65To ensure *HandlerSocket* is working as expected, you can follow these steps:
66
67Create a new table: ::
68
69 mysql> CREATE TABLE t (
70 id int(11) NOT NULL,
71 col varchar(20) NOT NULL,
72 PRIMARY KEY (id)
73 ) ENGINE=InnoDB;
74
75Insert a row with *HandlerSocket* (fields are separated by comma): ::
76
77 $ telnet 127.0.0.1 9999
78 Trying 127.0.0.1...
79 Connected to 127.0.0.1.
80 Escape character is '^]'.
81 P 1 test t PRIMARY id,col
82 0 1
83 1 + 2 1 test value
84 0 1
85
86And check in SQL that the row has been written: ::
87
88 mysql> SELECT * FROM t;
89 +----+------------+
90 | id | col |
91 +----+------------+
92 | 1 | test value |
93 +----+------------+
94
95Configuration options
96---------------------
97
98*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>`_.
99
100
101Other Reading
102=============
103
104 * Yoshinori Matsunobu's blog post describing `HandlerSocket <http://yoshinorimatsunobu.blogspot.com/2010/10/using-mysql-as-nosql-story-for.html>`_
105
106 * `Percona Server now both SQL and NOSQL <http://www.mysqlperformanceblog.com/2010/12/14/percona-server-now-both-sql-and-nosql/>`_
0107
=== added file 'doc/source/release-notes/Percona-Server-5.6.17-66.0.rst'
--- doc/source/release-notes/Percona-Server-5.6.17-66.0.rst 1970-01-01 00:00:00 +0000
+++ doc/source/release-notes/Percona-Server-5.6.17-66.0.rst 2014-06-09 16:20:30 +0000
@@ -0,0 +1,43 @@
1.. rn:: 5.6.17-66.0
2
3==============================
4 |Percona Server| 5.6.17-66.0
5==============================
6
7Percona 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>`).
8
9Based 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>`_.
10
11New Features
12============
13
14 |MySQL| benchmarks (``sql-bench`` directory in the |MySQL| distribution) has been made compatible with the TokuDB storage engine.
15
16 |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.
17
18 |Percona Server| has implemented ability to :ref:`clone a snapshot <snapshot_cloning>` created by ``START TRANSACTION WITH CONSISTENT SNAPSHOT`` in another session.
19
20 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.
21
22 |Percona Server| version 5.6 now includes :ref:`handlersocket_page` in addition to 5.5.
23
24Bugs Fixed
25==========
26
27 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`.
28
29 |InnoDB| could crash if workload contained writes to compressed tables. Bug fixed :bug:`1305364`.
30
31 GUI clients such as *MySQL Workbench* could not authenticate with a user defined with ``auth_pam_compat`` plugin. Bug fixed :bug:`1166938`.
32
33 Help in |Percona Server| 5.6 command line client was linking to |Percona Server| 5.1 manual. Bug fixed :bug:`1198775`.
34
35 |InnoDB| redo log resizing could crash when :ref:`changed_page_tracking` was enabled. Bug fixed :bug:`1204072`.
36
37 :ref:`audit_log_plugin` wasn't parsing escape characters correctly in the ``OLD`` format. Bug fixed :bug:`1313696`.
38
39 |Percona Server| version was reported incorrectly in *Debian*/*Ubuntu* packages. Bug fixed :bug:`1319670`.
40
41Other bugs fixed: :bug:`1318537` (upstream :mysqlbug:`72615`), :bug:`1318874`, :bug:`1285618`, :bug:`1272732`, :bug:`1314568`, :bug:`1271178`, and :bug:`1323014`.
42
43
044
=== modified file 'doc/source/release-notes/release-notes_index.rst'
--- doc/source/release-notes/release-notes_index.rst 2014-05-30 13:32:03 +0000
+++ doc/source/release-notes/release-notes_index.rst 2014-06-09 16:20:30 +0000
@@ -6,6 +6,7 @@
6 :maxdepth: 16 :maxdepth: 1
7 :glob:7 :glob:
88
9 Percona-Server-5.6.17-66.0
9 Percona-Server-5.6.17-65.010 Percona-Server-5.6.17-65.0
10 Percona-Server-5.6.16-64.2-tokudb11 Percona-Server-5.6.16-64.2-tokudb
11 Percona-Server-5.6.16-64.212 Percona-Server-5.6.16-64.2
1213
=== modified file 'doc/source/tokudb/tokudb_installation.rst'
--- doc/source/tokudb/tokudb_installation.rst 2014-03-27 07:04:17 +0000
+++ doc/source/tokudb/tokudb_installation.rst 2014-06-09 16:20:30 +0000
@@ -4,20 +4,48 @@
4 TokuDB Installation4 TokuDB Installation
5=====================5=====================
66
7.. warning:: 7.. note::
88
9 This feature is considered **BETA** quality and it isn't recommended for production use.9 This feature is considered **RELEASE CANDIDATE** quality and it isn't recommended for production use.
1010
11|Percona Server| has added support for TokuDB storage engine in the :rn:`5.6.16-64.0-tokudb` release.11|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.
1212
13`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.13`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.
1414
15TokuDB is currently supported only for 64-bit Linux distributions.15TokuDB is currently supported only for 64-bit Linux distributions.
1616
17Prerequisites
18=============
19
20``libjemalloc`` library
21-----------------------
22
23TokuDB 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.
24
25If 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: ::
26
27 [mysqld_safe]
28 malloc-lib= /path/to/jemalloc
29
30
31Transparent huge pages
32----------------------
33
34TokuDB 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: ::
35
36 $ cat /sys/kernel/mm/transparent_hugepage/enabled
37
38 [always] madvise never
39
40 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: ::
41
42 $ echo never > /sys/kernel/mm/transparent_hugepage/enabled
43 $ echo never > /sys/kernel/mm/transparent_hugepage/defrag
44
17Installation45Installation
18============46============
1947
20|Percona Server| with TokuDB is currently available in our :ref:`apt experimental <apt_repo>` and :ref:`yum testing <yum_repo>` repositories. 48TokuDB storage engine for |Percona Server| is currently available in our :ref:`apt <apt_repo>` and :ref:`yum <yum_repo>` repositories.
2149
22You can install the |Percona Server| with TokuDB engine by using the apt/yum commands:50You can install the |Percona Server| with TokuDB engine by using the apt/yum commands:
2351
@@ -25,38 +53,17 @@
2553
26 [root@centos ~]# yum install Percona-Server-tokudb-56.x86_6454 [root@centos ~]# yum install Percona-Server-tokudb-56.x86_64
2755
28or 56or
2957
30.. code-block:: bash58.. code-block:: bash
3159
32 root@wheezy:~# apt-get install percona-server-tokudb-5.660 root@wheezy:~# apt-get install percona-server-tokudb-5.6
3361
34.. note::62
3563Enabling the TokuDB Storage Engine
36 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: ::64==================================
37 65
38 $ cat /sys/kernel/mm/transparent_hugepage/enabled66This storage engine requires manual installation if there is a root password already set up during the new installation or upgrade.
39
40 [always] madvise never
41
42 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: ::
43
44 $ echo never > /sys/kernel/mm/transparent_hugepage/enabled
45 $ echo never > /sys/kernel/mm/transparent_hugepage/defrag
46
47
48Upgrade
49=======
50
51Upgrading 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).
52
53
54Manually enabling the TokuDB support
55====================================
56
57After |Percona Server| :rn:`5.6.16-64.2-tokudb` release, TokuDB engine will be automatically enabled during new installations.
58
59This plugin will require manual installation if there is a root password already set up during the new installation or upgrade.
6067
61.. code-block:: mysql68.. code-block:: mysql
6269
@@ -92,6 +99,36 @@
92 | TokuDB_lock_waits | ACTIVE | INFORMATION SCHEMA | ha_tokudb.so | GPL |99 | TokuDB_lock_waits | ACTIVE | INFORMATION SCHEMA | ha_tokudb.so | GPL |
93 ...100 ...
94101
102TokuDB Version
103==============
104
105TokuDB storage engine version can be checked with:
106
107.. code-block:: mysql
108
109 mysql> SELECT @@tokudb_version;
110 +------------------+
111 | @@tokudb_version |
112 +------------------+
113 | tokudb-7.1.7-rc7 |
114 +------------------+
115 1 row in set (0.00 sec)
116
117
118Upgrade
119=======
120
121Installing the TokuDB package is compatible with existing server setup and databases.
122
123Version Specific Information
124============================
125
126 * :rn:`5.6.16-64.0-tokudb`
127 TokuDB Storage engine available in special |Percona Server| release.
128 * :rn:`5.6.17-66.0`
129 TokuDB storage engine available as a separate |Percona Server| package.
130
131
95Other Reading132Other Reading
96=============133=============
97134
98135
=== modified file 'doc/source/tokudb/tokudb_intro.rst'
--- doc/source/tokudb/tokudb_intro.rst 2014-03-27 07:04:17 +0000
+++ doc/source/tokudb/tokudb_intro.rst 2014-06-09 16:20:30 +0000
@@ -4,11 +4,11 @@
4 TokuDB Introduction4 TokuDB Introduction
5=====================5=====================
66
7.. warning:: 7.. note::
88
9 This feature is considered **BETA** quality and it isn't recommended for production use.9 This feature is considered **RELEASE CANDIDATE** quality and it isn't recommended for production use.
1010
11|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.11|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.
1212
13TokuDB 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.13TokuDB 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.
1414
1515
=== modified file 'doc/source/upstream-bug-fixes.rst'
--- doc/source/upstream-bug-fixes.rst 2014-06-04 15:01:17 +0000
+++ doc/source/upstream-bug-fixes.rst 2014-06-09 16:20:30 +0000
@@ -5,15 +5,21 @@
5=============================================================5=============================================================
66
7+-------------------------------------------------------------------------------------------------------------+7+-------------------------------------------------------------------------------------------------------------+
8|:Upstream bug: :mysqlbug:`72615` - MTR --mysqld=--default-storage-engine=foo incompatible w/ dynamically... |
9|:Launchpad bug: :bug:`1318537` |
10|:Upstream state: Verified (checked on 2014-06-09) |
11|:Fix Released: :rn:`5.6.17-66.0` |
12|:Upstream fix: N/A |
13+-------------------------------------------------------------------------------------------------------------+
8|:Upstream bug: :mysqlbug:`72163` - Rev 5774 broke rpl_plugin_load |14|:Upstream bug: :mysqlbug:`72163` - Rev 5774 broke rpl_plugin_load |
9|:Launchpad bug: :bug:`1299688` |15|:Launchpad bug: :bug:`1299688` |
10|:Upstream state: Verified (checked on 2014-04-30) |16|:Upstream state: Verified (checked on 2014-06-09) |
11|:Fix Released: :rn:`5.6.17-65.0` |17|:Fix Released: :rn:`5.6.17-65.0` |
12|:Upstream fix: N/A |18|:Upstream fix: N/A |
13+-------------------------------------------------------------------------------------------------------------+19+-------------------------------------------------------------------------------------------------------------+
14|:Upstream bug: :mysqlbug:`60782` - Audit plugin API: no MYSQL_AUDIT_GENERAL_LOG notifications with general...|20|:Upstream bug: :mysqlbug:`60782` - Audit plugin API: no MYSQL_AUDIT_GENERAL_LOG notifications with general...|
15|:Launchpad bug: :bug:`1182535` |21|:Launchpad bug: :bug:`1182535` |
16|:Upstream state: Verified (checked on 2014-04-30) |22|:Upstream state: Verified (checked on 2014-06-09) |
17|:Fix Released: :rn:`5.6.17-65.0` |23|:Fix Released: :rn:`5.6.17-65.0` |
18|:Upstream fix: N/A |24|:Upstream fix: N/A |
19+-------------------------------------------------------------------------------------------------------------+25+-------------------------------------------------------------------------------------------------------------+
@@ -25,19 +31,19 @@
25+-------------------------------------------------------------------------------------------------------------+31+-------------------------------------------------------------------------------------------------------------+
26|:Upstream bug: :mysqlbug:`71374` - Slave IO thread won't attempt auto reconnect to the master/error-code 1159|32|:Upstream bug: :mysqlbug:`71374` - Slave IO thread won't attempt auto reconnect to the master/error-code 1159|
27|:Launchpad bug: :bug:`1268729` |33|:Launchpad bug: :bug:`1268729` |
28|:Upstream state: Verified (checked on 2014-04-30) |34|:Upstream state: Verified (checked on 2014-06-09) |
29|:Fix Released: :rn:`5.6.16-64.1` |35|:Fix Released: :rn:`5.6.16-64.1` |
30|:Upstream fix: N/A |36|:Upstream fix: N/A |
31+-------------------------------------------------------------------------------------------------------------+37+-------------------------------------------------------------------------------------------------------------+
32|:Upstream bug: :mysqlbug:`71988` - page_cleaner: aggressive background flushing |38|:Upstream bug: :mysqlbug:`71988` - page_cleaner: aggressive background flushing |
33|:Launchpad bug: :bug:`1238039` |39|:Launchpad bug: :bug:`1238039` |
34|:Upstream state: Verified (checked on 2014-04-30) |40|:Upstream state: Verified (checked on 2014-06-09) |
35|:Fix Released: :rn:`5.6.16-64.0` |41|:Fix Released: :rn:`5.6.16-64.0` |
36|:Upstream fix: N/A |42|:Upstream fix: N/A |
37+-------------------------------------------------------------------------------------------------------------+43+-------------------------------------------------------------------------------------------------------------+
38|:Upstream bug: :mysqlbug:`71624` - printf size_t results in a fatal warning in 32-bit debug builds |44|:Upstream bug: :mysqlbug:`71624` - printf size_t results in a fatal warning in 32-bit debug builds |
39|:Launchpad bug: :bug:`1277505` |45|:Launchpad bug: :bug:`1277505` |
40|:Upstream state: Can't repeat (checked on 2014-04-30) |46|:Upstream state: Can't repeat (checked on 2014-06-09) |
41|:Fix Released: :rn:`5.6.16-64.0` |47|:Fix Released: :rn:`5.6.16-64.0` |
42|:Upstream fix: N/A |48|:Upstream fix: N/A |
43+-------------------------------------------------------------------------------------------------------------+49+-------------------------------------------------------------------------------------------------------------+
@@ -79,13 +85,13 @@
79+-------------------------------------------------------------------------------------------------------------+85+-------------------------------------------------------------------------------------------------------------+
80|:Upstream bug: :mysqlbug:`71270` - Failures to end bulk insert for partitioned tables handled incorrectly |86|:Upstream bug: :mysqlbug:`71270` - Failures to end bulk insert for partitioned tables handled incorrectly |
81|:Launchpad bug: :bug:`1204871` |87|:Launchpad bug: :bug:`1204871` |
82|:Upstream state: Verified (checked on 2014-04-30) |88|:Upstream state: Verified (checked on 2014-06-09) |
83|:Fix Released: :rn:`5.6.16-64.0` |89|:Fix Released: :rn:`5.6.16-64.0` |
84|:Upstream fix: N/A |90|:Upstream fix: N/A |
85+-------------------------------------------------------------------------------------------------------------+91+-------------------------------------------------------------------------------------------------------------+
86|:Upstream bug: :mysqlbug:`71217` - Threadpool - add thd_wait_begin/thd_wait_end to the network IO functions |92|:Upstream bug: :mysqlbug:`71217` - Threadpool - add thd_wait_begin/thd_wait_end to the network IO functions |
87|:Launchpad bug: :bug:`1159743` |93|:Launchpad bug: :bug:`1159743` |
88|:Upstream state: Open (checked on 2014-04-30) |94|:Upstream state: Open (checked on 2014-06-09) |
89|:Fix Released: :rn:`5.6.15-63.0` |95|:Fix Released: :rn:`5.6.15-63.0` |
90|:Upstream fix: N/A |96|:Upstream fix: N/A |
91+-------------------------------------------------------------------------------------------------------------+97+-------------------------------------------------------------------------------------------------------------+
@@ -103,7 +109,7 @@
103+-------------------------------------------------------------------------------------------------------------+109+-------------------------------------------------------------------------------------------------------------+
104|:Upstream bug: :mysqlbug:`71411` - buf_flush_LRU() does not return correct number in case of compressed pages|110|:Upstream bug: :mysqlbug:`71411` - buf_flush_LRU() does not return correct number in case of compressed pages|
105|:Launchpad bug: :bug:`1231918` |111|:Launchpad bug: :bug:`1231918` |
106|:Upstream state: Verified (checked on 2014-04-30) |112|:Upstream state: Verified (checked on 2014-06-09) |
107|:Fix Released: :rn:`5.6.13-61.0` |113|:Fix Released: :rn:`5.6.13-61.0` |
108|:Upstream fix: N/A |114|:Upstream fix: N/A |
109+-------------------------------------------------------------------------------------------------------------+115+-------------------------------------------------------------------------------------------------------------+
@@ -115,7 +121,7 @@
115+-------------------------------------------------------------------------------------------------------------+121+-------------------------------------------------------------------------------------------------------------+
116|:Upstream bug: :mysqlbug:`70490` - Suppression is too strict on some systems |122|:Upstream bug: :mysqlbug:`70490` - Suppression is too strict on some systems |
117|:Launchpad bug: :bug:`1205196` |123|:Launchpad bug: :bug:`1205196` |
118|:Upstream state: No Feedback (checked on 2014-04-30) |124|:Upstream state: No Feedback (checked on 2014-06-09) |
119|:Fix Released: :rn:`5.6.13-61.0` |125|:Fix Released: :rn:`5.6.13-61.0` |
120|:Upstream fix: N/A |126|:Upstream fix: N/A |
121+-------------------------------------------------------------------------------------------------------------+127+-------------------------------------------------------------------------------------------------------------+
@@ -127,7 +133,7 @@
127+-------------------------------------------------------------------------------------------------------------+133+-------------------------------------------------------------------------------------------------------------+
128|:Upstream bug: :mysqlbug:`70500` - Page cleaner should perform LRU flushing regardless of server activity |134|:Upstream bug: :mysqlbug:`70500` - Page cleaner should perform LRU flushing regardless of server activity |
129|:Launchpad bug: :bug:`1234562` |135|:Launchpad bug: :bug:`1234562` |
130|:Upstream state: Open (checked on 2014-04-30) |136|:Upstream state: Open (checked on 2014-06-09) |
131|:Fix Released: :rn:`5.6.13-61.0` |137|:Fix Released: :rn:`5.6.13-61.0` |
132|:Upstream fix: N/A |138|:Upstream fix: N/A |
133+-------------------------------------------------------------------------------------------------------------+139+-------------------------------------------------------------------------------------------------------------+
@@ -145,31 +151,31 @@
145+-------------------------------------------------------------------------------------------------------------+151+-------------------------------------------------------------------------------------------------------------+
146|:Upstream bug: :mysqlbug:`68481` - InnoDB LRU flushing for MySQL 5.6 needs work |152|:Upstream bug: :mysqlbug:`68481` - InnoDB LRU flushing for MySQL 5.6 needs work |
147|:Launchpad bug: :bug:`1232406` |153|:Launchpad bug: :bug:`1232406` |
148|:Upstream state: Verified (checked on 2014-04-30) |154|:Upstream state: Verified (checked on 2014-06-09) |
149|:Fix Released: :rn:`5.6.13-61.0` |155|:Fix Released: :rn:`5.6.13-61.0` |
150|:Upstream fix: N/A |156|:Upstream fix: N/A |
151+-------------------------------------------------------------------------------------------------------------+157+-------------------------------------------------------------------------------------------------------------+
152|:Upstream bug: :mysqlbug:`70453` - Add hard timeouts to page cleaner flushes |158|:Upstream bug: :mysqlbug:`70453` - Add hard timeouts to page cleaner flushes |
153|:Launchpad bug: :bug:`1232101` |159|:Launchpad bug: :bug:`1232101` |
154|:Upstream state: Verified (checked on 2014-04-30) |160|:Upstream state: Verified (checked on 2014-06-09) |
155|:Fix Released: :rn:`5.6.13-61.0` |161|:Fix Released: :rn:`5.6.13-61.0` |
156|:Upstream fix: N/A |162|:Upstream fix: N/A |
157+-------------------------------------------------------------------------------------------------------------+163+-------------------------------------------------------------------------------------------------------------+
158|:Upstream bug: :mysqlbug:`69170` - buf_flush_LRU is lazy |164|:Upstream bug: :mysqlbug:`69170` - buf_flush_LRU is lazy |
159|:Launchpad bug: :bug:`1231918` |165|:Launchpad bug: :bug:`1231918` |
160|:Upstream state: Verified (checked on 2014-04-30) |166|:Upstream state: Verified (checked on 2014-06-09) |
161|:Fix Released: :rn:`5.6.13-61.0` |167|:Fix Released: :rn:`5.6.13-61.0` |
162|:Upstream fix: N/A |168|:Upstream fix: N/A |
163+-------------------------------------------------------------------------------------------------------------+169+-------------------------------------------------------------------------------------------------------------+
164|:Upstream bug: :mysqlbug:`68555` - thread convoys from log_checkpoint_margin with innodb_buffer_pool_inst... |170|:Upstream bug: :mysqlbug:`68555` - thread convoys from log_checkpoint_margin with innodb_buffer_pool_inst... |
165|:Launchpad bug: :bug:`1236884` |171|:Launchpad bug: :bug:`1236884` |
166|:Upstream state: Verified (checked on 2014-04-30) |172|:Upstream state: Verified (checked on 2014-06-09) |
167|:Fix Released: :rn:`5.6.13-61.0` |173|:Fix Released: :rn:`5.6.13-61.0` |
168|:Upstream fix: N/A |174|:Upstream fix: N/A |
169+-------------------------------------------------------------------------------------------------------------+175+-------------------------------------------------------------------------------------------------------------+
170|:Upstream bug: :mysqlbug:`70228` - Is buf_LRU_free_page() really supposed to make non-zip block sticky at ...|176|:Upstream bug: :mysqlbug:`70228` - Is buf_LRU_free_page() really supposed to make non-zip block sticky at ...|
171|:Launchpad bug: :bug:`1220544` |177|:Launchpad bug: :bug:`1220544` |
172|:Upstream state: Verified (checked on 2014-04-30) |178|:Upstream state: Verified (checked on 2014-06-09) |
173|:Fix Released: :rn:`5.6.13-60.6` |179|:Fix Released: :rn:`5.6.13-60.6` |
174|:Upstream fix: N/A |180|:Upstream fix: N/A |
175+-------------------------------------------------------------------------------------------------------------+181+-------------------------------------------------------------------------------------------------------------+
@@ -187,13 +193,13 @@
187+-------------------------------------------------------------------------------------------------------------+193+-------------------------------------------------------------------------------------------------------------+
188|:Upstream bug: :mysqlbug:`70216` - Unnecessary overhead from persistent adaptive hash index latches |194|:Upstream bug: :mysqlbug:`70216` - Unnecessary overhead from persistent adaptive hash index latches |
189|:Launchpad bug: :bug:`1218347` |195|:Launchpad bug: :bug:`1218347` |
190|:Upstream state: Verified (checked on 2014-04-30) |196|:Upstream state: Verified (checked on 2014-06-09) |
191|:Fix Released: :rn:`5.6.13-60.6` |197|:Fix Released: :rn:`5.6.13-60.6` |
192|:Upstream fix: N/A |198|:Upstream fix: N/A |
193+-------------------------------------------------------------------------------------------------------------+199+-------------------------------------------------------------------------------------------------------------+
194|:Upstream bug: :mysqlbug:`62018` - innodb adaptive hash index mutex contention |200|:Upstream bug: :mysqlbug:`62018` - innodb adaptive hash index mutex contention |
195|:Launchpad bug: :bug:`1216804` |201|:Launchpad bug: :bug:`1216804` |
196|:Upstream state: Verified (checked on 2014-04-30) |202|:Upstream state: Verified (checked on 2014-06-09) |
197|:Fix Released: :rn:`5.6.13-60.6` |203|:Fix Released: :rn:`5.6.13-60.6` |
198|:Upstream fix: N/A |204|:Upstream fix: N/A |
199+-------------------------------------------------------------------------------------------------------------+205+-------------------------------------------------------------------------------------------------------------+
@@ -211,13 +217,13 @@
211+-------------------------------------------------------------------------------------------------------------+217+-------------------------------------------------------------------------------------------------------------+
212|:Upstream bug: :mysqlbug:`42415` - UPDATE/DELETE with LIMIT clause unsafe for SBL even with ORDER BY PK ... |218|:Upstream bug: :mysqlbug:`42415` - UPDATE/DELETE with LIMIT clause unsafe for SBL even with ORDER BY PK ... |
213|:Launchpad bug: :bug:`1132194` |219|:Launchpad bug: :bug:`1132194` |
214|:Upstream state: Verified (checked on 2014-04-30) |220|:Upstream state: Verified (checked on 2014-06-09) |
215|:Fix Released: :rn:`5.6.13-60.5` |221|:Fix Released: :rn:`5.6.13-60.5` |
216|:Upstream fix: N/A |222|:Upstream fix: N/A |
217+-------------------------------------------------------------------------------------------------------------+223+-------------------------------------------------------------------------------------------------------------+
218|:Upstream bug: :mysqlbug:`69639` - mysql failed to build with dtrace Sun D 1.11 |224|:Upstream bug: :mysqlbug:`69639` - mysql failed to build with dtrace Sun D 1.11 |
219|:Launchpad bug: :bug:`1196460` |225|:Launchpad bug: :bug:`1196460` |
220|:Upstream state: Open (checked on 2014-04-30) |226|:Upstream state: Open (checked on 2014-06-09) |
221|:Fix Released: :rn:`5.6.13-60.5` |227|:Fix Released: :rn:`5.6.13-60.5` |
222|:Upstream fix: N/A |228|:Upstream fix: N/A |
223+-------------------------------------------------------------------------------------------------------------+229+-------------------------------------------------------------------------------------------------------------+
@@ -235,7 +241,7 @@
235+-------------------------------------------------------------------------------------------------------------+241+-------------------------------------------------------------------------------------------------------------+
236|:Upstream bug: :mysqlbug:`69856` - mysql_install_db does not function properly in 5.6 for debug builds |242|:Upstream bug: :mysqlbug:`69856` - mysql_install_db does not function properly in 5.6 for debug builds |
237|:Launchpad bug: :bug:`1179359` |243|:Launchpad bug: :bug:`1179359` |
238|:Upstream state: Verified (checked on 2014-04-30) |244|:Upstream state: Verified (checked on 2014-06-09) |
239|:Fix Released: :rn:`5.6.12-60.4` |245|:Fix Released: :rn:`5.6.12-60.4` |
240|:Upstream fix: N/A |246|:Upstream fix: N/A |
241+-------------------------------------------------------------------------------------------------------------+247+-------------------------------------------------------------------------------------------------------------+
@@ -247,7 +253,7 @@
247+-------------------------------------------------------------------------------------------------------------+253+-------------------------------------------------------------------------------------------------------------+
248|:Upstream bug: :mysqlbug:`71183` - os_file_fsync() should handle fsync() returning EINTR |254|:Upstream bug: :mysqlbug:`71183` - os_file_fsync() should handle fsync() returning EINTR |
249|:Launchpad bug: :bug:`1262651` |255|:Launchpad bug: :bug:`1262651` |
250|:Upstream state: Verified (checked on 2014-04-30) |256|:Upstream state: Verified (checked on 2014-06-09) |
251|:Fix Released: :rn:`5.6.11-60.3` |257|:Fix Released: :rn:`5.6.11-60.3` |
252|:Upstream fix: N/A |258|:Upstream fix: N/A |
253+-------------------------------------------------------------------------------------------------------------+259+-------------------------------------------------------------------------------------------------------------+
@@ -277,7 +283,7 @@
277+-------------------------------------------------------------------------------------------------------------+283+-------------------------------------------------------------------------------------------------------------+
278|:Upstream bug: :mysqlbug:`68714` - Remove literal statement digest values from perfschema tests |284|:Upstream bug: :mysqlbug:`68714` - Remove literal statement digest values from perfschema tests |
279|:Launchpad bug: :bug:`1157078` |285|:Launchpad bug: :bug:`1157078` |
280|:Upstream state: Verified (checked on 2014-04-30) |286|:Upstream state: Verified (checked on 2014-06-09) |
281|:Fix Released: :rn:`5.6.11-60.3` |287|:Fix Released: :rn:`5.6.11-60.3` |
282|:Upstream fix: N/A |288|:Upstream fix: N/A |
283+-------------------------------------------------------------------------------------------------------------+289+-------------------------------------------------------------------------------------------------------------+
@@ -301,13 +307,13 @@
301+-------------------------------------------------------------------------------------------------------------+307+-------------------------------------------------------------------------------------------------------------+
302|:Upstream bug: :mysqlbug:`68970` - fsp_reserve_free_extents switches from small to big tblspace handling ... |308|:Upstream bug: :mysqlbug:`68970` - fsp_reserve_free_extents switches from small to big tblspace handling ... |
303|:Launchpad bug: :bug:`1169494` |309|:Launchpad bug: :bug:`1169494` |
304|:Upstream state: Verified (checked on 2014-04-30) |310|:Upstream state: Verified (checked on 2014-06-09) |
305|:Fix Released: :rn:`5.6.11-60.3` |311|:Fix Released: :rn:`5.6.11-60.3` |
306|:Upstream fix: N/A |312|:Upstream fix: N/A |
307+-------------------------------------------------------------------------------------------------------------+313+-------------------------------------------------------------------------------------------------------------+
308|:Upstream bug: :mysqlbug:`68713` - create_duplicate_weedout_tmp_table() leaves key_part_flag uninitialized |314|:Upstream bug: :mysqlbug:`68713` - create_duplicate_weedout_tmp_table() leaves key_part_flag uninitialized |
309|:Launchpad bug: :bug:`1157037` |315|:Launchpad bug: :bug:`1157037` |
310|:Upstream state: Verified (checked on 2014-04-30) |316|:Upstream state: Verified (checked on 2014-06-09) |
311|:Fix Released: :rn:`5.6.11-60.3` |317|:Fix Released: :rn:`5.6.11-60.3` |
312|:Upstream fix: N/A |318|:Upstream fix: N/A |
313+-------------------------------------------------------------------------------------------------------------+319+-------------------------------------------------------------------------------------------------------------+
@@ -319,13 +325,13 @@
319+-------------------------------------------------------------------------------------------------------------+325+-------------------------------------------------------------------------------------------------------------+
320|:Upstream bug: :mysqlbug:`68999` - SSL_OP_NO_COMPRESSION not defined |326|:Upstream bug: :mysqlbug:`68999` - SSL_OP_NO_COMPRESSION not defined |
321|:Launchpad bug: :bug:`1183610` |327|:Launchpad bug: :bug:`1183610` |
322|:Upstream state: No Feedback (checked on 2014-04-30) |328|:Upstream state: No Feedback (checked on 2014-06-09) |
323|:Fix Released: :rn:`5.6.11-60.3` |329|:Fix Released: :rn:`5.6.11-60.3` |
324|:Upstream fix: N/A |330|:Upstream fix: N/A |
325+-------------------------------------------------------------------------------------------------------------+331+-------------------------------------------------------------------------------------------------------------+
326|:Upstream bug: :mysqlbug:`68845` - Unnecessary log_sys->mutex reacquisition in mtr_log_reserve_and_write() |332|:Upstream bug: :mysqlbug:`68845` - Unnecessary log_sys->mutex reacquisition in mtr_log_reserve_and_write() |
327|:Launchpad bug: :bug:`1163439` |333|:Launchpad bug: :bug:`1163439` |
328|:Upstream state: Verified (checked on 2014-04-30) |334|:Upstream state: Verified (checked on 2014-06-09) |
329|:Fix Released: :rn:`5.6.11-60.3` |335|:Fix Released: :rn:`5.6.11-60.3` |
330|:Upstream fix: N/A |336|:Upstream fix: N/A |
331+-------------------------------------------------------------------------------------------------------------+337+-------------------------------------------------------------------------------------------------------------+
@@ -355,7 +361,7 @@
355+-------------------------------------------------------------------------------------------------------------+361+-------------------------------------------------------------------------------------------------------------+
356|:Upstream bug: :mysqlbug:`68476` - Suboptimal code in my_strnxfrm_simple() |362|:Upstream bug: :mysqlbug:`68476` - Suboptimal code in my_strnxfrm_simple() |
357|:Launchpad bug: :bug:`1132350` |363|:Launchpad bug: :bug:`1132350` |
358|:Upstream state: Verified (checked on 2014-04-30) |364|:Upstream state: Verified (checked on 2014-06-09) |
359|:Fix Released: :rn:`5.6.11-60.3` |365|:Fix Released: :rn:`5.6.11-60.3` |
360|:Upstream fix: N/A |366|:Upstream fix: N/A |
361+-------------------------------------------------------------------------------------------------------------+367+-------------------------------------------------------------------------------------------------------------+
@@ -415,7 +421,7 @@
415+-------------------------------------------------------------------------------------------------------------+421+-------------------------------------------------------------------------------------------------------------+
416|:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|422|:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|
417|:Launchpad bug: :bug:`1042517` |423|:Launchpad bug: :bug:`1042517` |
418|:Upstream state: Verified (checked on 2014-04-30) |424|:Upstream state: Verified (checked on 2014-06-09) |
419|:Fix Released: :rn:`5.6.11-60.3` |425|:Fix Released: :rn:`5.6.11-60.3` |
420|:Upstream fix: N/A |426|:Upstream fix: N/A |
421+-------------------------------------------------------------------------------------------------------------+427+-------------------------------------------------------------------------------------------------------------+
@@ -427,7 +433,7 @@
427+-------------------------------------------------------------------------------------------------------------+433+-------------------------------------------------------------------------------------------------------------+
428|:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no. | 434|:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no. |
429|:Launchpad bug: :bug:`1013432` |435|:Launchpad bug: :bug:`1013432` |
430|:Upstream state: Verified (checked on 2014-04-30) |436|:Upstream state: Verified (checked on 2014-06-09) |
431|:Fix Released: :rn:`5.6.11-60.3` |437|:Fix Released: :rn:`5.6.11-60.3` |
432|:Upstream fix: N/A |438|:Upstream fix: N/A |
433+-------------------------------------------------------------------------------------------------------------+439+-------------------------------------------------------------------------------------------------------------+
@@ -457,13 +463,13 @@
457+-------------------------------------------------------------------------------------------------------------+463+-------------------------------------------------------------------------------------------------------------+
458|:Upstream bug: :mysqlbug:`25007` - memory tables with dynamic rows format |464|:Upstream bug: :mysqlbug:`25007` - memory tables with dynamic rows format |
459|:Launchpad bug: N/A |465|:Launchpad bug: N/A |
460|:Upstream state: Verified (checked on 2014-04-30) |466|:Upstream state: Verified (checked on 2014-06-09) |
461|:Fix Released: :rn:`5.6.11-60.3` |467|:Fix Released: :rn:`5.6.11-60.3` |
462|:Upstream fix: N/A |468|:Upstream fix: N/A |
463+-------------------------------------------------------------------------------------------------------------+469+-------------------------------------------------------------------------------------------------------------+
464|:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |470|:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |
465|:Launchpad bug: :bug:`800035` |471|:Launchpad bug: :bug:`800035` |
466|:Upstream state: Verified (checked on 2014-04-30) |472|:Upstream state: Verified (checked on 2014-06-09) |
467|:Fix Released: :rn:`5.6.11-60.3` |473|:Fix Released: :rn:`5.6.11-60.3` |
468|:Upstream fix: N/A |474|:Upstream fix: N/A |
469+-------------------------------------------------------------------------------------------------------------+475+-------------------------------------------------------------------------------------------------------------+
@@ -475,7 +481,7 @@
475+-------------------------------------------------------------------------------------------------------------+481+-------------------------------------------------------------------------------------------------------------+
476|:Upstream bug: :mysqlbug:`68116` - InnoDB monitor may hit an assertion error in buf_page_get_gen in debug ...|482|:Upstream bug: :mysqlbug:`68116` - InnoDB monitor may hit an assertion error in buf_page_get_gen in debug ...|
477|:Launchpad bug: :bug:`1100178` |483|:Launchpad bug: :bug:`1100178` |
478|:Upstream state: Verified (checked on 2014-04-30) |484|:Upstream state: Verified (checked on 2014-06-09) |
479|:Fix Released: :rn:`5.6.10-60.2` |485|:Fix Released: :rn:`5.6.10-60.2` |
480|:Upstream fix: N/A |486|:Upstream fix: N/A |
481+-------------------------------------------------------------------------------------------------------------+487+-------------------------------------------------------------------------------------------------------------+
@@ -487,13 +493,13 @@
487+-------------------------------------------------------------------------------------------------------------+493+-------------------------------------------------------------------------------------------------------------+
488|:Upstream bug: :mysqlbug:`20001` - Support for temp-tables in INFORMATION_SCHEMA |494|:Upstream bug: :mysqlbug:`20001` - Support for temp-tables in INFORMATION_SCHEMA |
489|:Launchpad bug: N/A |495|:Launchpad bug: N/A |
490|:Upstream state: Verified (checked on 2014-04-30) |496|:Upstream state: Verified (checked on 2014-06-09) |
491|:Fix Released: :rn:`5.6.5-60.0` |497|:Fix Released: :rn:`5.6.5-60.0` |
492|:Upstream fix: N/A |498|:Upstream fix: N/A |
493+-------------------------------------------------------------------------------------------------------------+499+-------------------------------------------------------------------------------------------------------------+
494|:Upstream bug: :mysqlbug:`69146` - Optimization in buf_pool_get_oldest_modification if srv_buf_pool_instances|500|:Upstream bug: :mysqlbug:`69146` - Optimization in buf_pool_get_oldest_modification if srv_buf_pool_instances|
495|:Launchpad bug: :bug:`1176496` |501|:Launchpad bug: :bug:`1176496` |
496|:Upstream state: Open (checked on 2014-04-30) |502|:Upstream state: Verified (checked on 2014-06-09) |
497|:Fix Released: :rn:`5.6.5-60.0` |503|:Fix Released: :rn:`5.6.5-60.0` |
498|:Upstream fix: N/A |504|:Upstream fix: N/A |
499+-------------------------------------------------------------------------------------------------------------+505+-------------------------------------------------------------------------------------------------------------+

Subscribers

People subscribed via source and target branches