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

Merge lp:~hrvojem/percona-server/rn-5.1.73-14.11-5.6 into lp:percona-server/5.6

  1. rn-5.1.73-14.11-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: 520
Proposed branch: lp:~hrvojem/percona-server/rn-5.1.73-14.11-5.6
Merge into: lp:percona-server/5.6
Diff against target: 561 lines (+207/-46)
10 files modified
doc/source/conf.py (+1/-1)
doc/source/flexibility/extended_mysqlbinlog.rst (+29/-0)
doc/source/index.rst (+1/-0)
doc/source/installation/apt_repo.rst (+1/-0)
doc/source/performance/threadpool.rst (+60/-5)
doc/source/ps-versions-comparison.rst (+3/-0)
doc/source/release-notes/Percona-Server-5.6.15-63.0.rst (+53/-0)
doc/source/release-notes/release-notes_index.rst (+1/-0)
doc/source/upgrading_guide_55_56.rst (+3/-3)
doc/source/upstream-bug-fixes.rst (+55/-37)
To merge this branch: bzr merge lp:~hrvojem/percona-server/rn-5.1.73-14.11-5.6
Reviewer Review Type Date Requested Status
Laurynas Biveinis (community) Approve
Review via email: mp+199639@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

   - same note about userstat as in the 5.5 RN review
   - bug 1159743 changes deserve a note in threadpool.rst too?
   - 219: s/io/I/O
some bugs need descriptions, below are some needing-improvement drafts:
   - 1236696: server performance could degrade under heavy load or it
     could deadlock on shutdown while performing purge
   - 1240371: server could crash under heavy load if InnoDB
     compression was used
   - 1250148: redo log checksum mismatches would be diagnosed using
     the data page checksum algorithm setting instead of redo log
     checksum algorithm one

review: Needs Fixing
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

   - The network wait note in threadpool docs should not fall under
     "Priority Connection Scheduling" section as it does currently.
     Probably it should get own section "Handling of Long Network
     Waits" or similar.
   - Where are the release notes?

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 2013-12-16 08:45:31 +0000
3+++ doc/source/conf.py 2013-12-19 13:41:48 +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.14-62.0'
9+release = '5.6.15-63.0'
10
11 # The language for content autogenerated by Sphinx. Refer to documentation
12 # for a list of supported languages.
13
14=== added file 'doc/source/flexibility/extended_mysqlbinlog.rst'
15--- doc/source/flexibility/extended_mysqlbinlog.rst 1970-01-01 00:00:00 +0000
16+++ doc/source/flexibility/extended_mysqlbinlog.rst 2013-12-19 13:41:48 +0000
17@@ -0,0 +1,29 @@
18+.. _extended_mysqlbinlog:
19+
20+=========================
21+ Extended ``mysqlbinlog``
22+=========================
23+
24+|Percona Server| has implemented compression support for :command:`mysqlbinlog` in :rn:`5.6.15-63.0`. This is similar to support that both ``mysql`` and ``mysqldump`` programs include (the ``-C``, ``--compress`` options "Use compression in server/client protocol"). Using the compressed protocol helps reduce the bandwidth use and speed up transfers.
25+
26+|Percona Server| has also implemented support for ``SSL``. :command:`mysqlbinlog` now accepts the ``SSL`` connection options as all the other client programs. This feature can be useful with ``--read-from-remote-server`` option. Following ``SSL`` options are now available:
27+
28+ * :option:`--ssl` - Enable SSL for connection (automatically enabled with other flags).
29+ * :option:`--ssl-ca=name` - CA file in PEM format (check OpenSSL docs, implies --ssl).
30+ * :option:`--ssl-capath=name` - CA directory (check OpenSSL docs, implies --ssl).
31+ * :option:`--ssl-cert=name` - X509 cert in PEM format (implies --ssl).
32+ * :option:`--ssl-cipher=name` - SSL cipher to use (implies --ssl).
33+ * :option:`--ssl-key=name` - X509 key in PEM format (implies --ssl).
34+ * :option:`--ssl-verify-server-cert` - Verify server's "Common Name" in its cert against hostname used when connecting. This option is disabled by default.
35+
36+Version Specific Information
37+============================
38+
39+ * :rn:`5.6.15-63.0`
40+ :command:`mysqlbinlog` option :option:`--compress` introduced
41+
42+
43+ * :rn:`5.6.15-63.0`
44+ :command:`mysqlbinlog` now has all SSL connection options as the rest of the |MySQL| client programs.
45+
46+
47
48=== modified file 'doc/source/index.rst'
49--- doc/source/index.rst 2013-12-16 08:45:31 +0000
50+++ doc/source/index.rst 2013-12-19 13:41:48 +0000
51@@ -89,6 +89,7 @@
52 flexibility/buff_read_ahead_area
53 flexibility/extended_select_into_outfile
54 flexibility/per_query_variable_statement
55+ flexibility/extended_mysqlbinlog
56
57 Reliability Improvements
58 ========================
59
60=== modified file 'doc/source/installation/apt_repo.rst'
61--- doc/source/installation/apt_repo.rst 2013-07-03 09:35:35 +0000
62+++ doc/source/installation/apt_repo.rst 2013-12-19 13:41:48 +0000
63@@ -39,6 +39,7 @@
64 * 12.04LTS (precise)
65 * 12.10 (quantal)
66 * 13.04 (raring)
67+ * 13.10 (saucy)
68
69
70 Release Candidate Repository
71
72=== modified file 'doc/source/performance/threadpool.rst'
73--- doc/source/performance/threadpool.rst 2013-07-12 08:38:41 +0000
74+++ doc/source/performance/threadpool.rst 2013-12-19 13:41:48 +0000
75@@ -40,7 +40,27 @@
76
77 The goal is to minimize the number of open transactions in the server. In many cases it is beneficial to give short-running transactions a chance to commit faster and thus deallocate server resources and locks without waiting in the same queue with other connections that are about to start a new transaction, or those that have run out of their high priority tickets.
78
79-With the default value of 0, all connections are always put into the common queue, i.e. no priority scheduling is used as in the original implementation in |MariaDB|. The higher is the value, the more chances each transaction gets to enter the high priority queue and commit before it is put in the common queue.
80+The default thread pool behavior is to always put events from already started transactions into the high priority queue, as we believe that results in better performance in vast majority of cases.
81+
82+With the value of ``0``, all connections are always put into the common queue, i.e. no priority scheduling is used as in the original implementation in |MariaDB|. The higher is the value, the more chances each transaction gets to enter the high priority queue and commit before it is put in the common queue.
83+
84+In some cases it is required to prioritize all statements for a specific connection regardless of whether they are executed as a part of a multi-statement transaction or in the autocommit mode. Or vice versa, some connections may require using the low priority queue for all statements unconditionally. To implement this new :variable:`thread_pool_high_prio_mode` variable has been introduced in |Percona Server| :rn:`5.6.15-63.0`.
85+
86+.. _low_priority_queue_throttling:
87+
88+Low priority queue throttling
89+-----------------------------
90+
91+One case that can limit thread pool performance and even lead to deadlocks under high concurrency is a situation when thread groups are oversubscribed due to active threads reaching the oversubscribe limit, but all/most worker threads are actually waiting on locks currently held by a transaction from another connection that is not currently in the thread pool.
92+
93+What happens in this case is that those threads in the pool that have marked themselves inactive are not accounted to the oversubscribe limit. As a result, the number of threads (both active and waiting) in the pool grows until it hits :variable:`thread_pool_max_threads` value. If the connection executing the transaction which is holding the lock has managed to enter the thread pool by then, we get a large (depending on the :variable:`thread_pool_max_threads` value) number of concurrently running threads, and thus, suboptimal performance as a result. Otherwise, we get a deadlock as no more threads can be created to process those transaction(s) and release the lock(s).
94+
95+Such situations are prevented by throttling the low priority queue when the total number of worker threads (both active and waiting ones) reaches the oversubscribe limit. That is, if there are too many worker threads, do not start new transactions and create new threads until queued events from the already started transactions are processed.
96+
97+Handling of Long Network Waits
98+==============================
99+
100+Certain types of workloads (large result sets, BLOBs, slow clients) can have longer waits on network I/O (socket reads and writes). Whenever server waits, this should be communicated to the Thread Pool, so it can start new query by either waking a waiting thread or sometimes creating a new one. This implementation has been ported from |MariaDB| patch `MDEV-156 <https://mariadb.atlassian.net/browse/MDEV-156>`_ in |Percona Server| :rn:`5.6.15-63.0`.
101
102
103 Version Specific Information
104@@ -52,6 +72,21 @@
105 * :rn:`5.6.11-60.3`
106 Implemented priority connection scheduling and introduced new variable :variable:`thread_pool_high_prio_tickets` to the original implementation introduced in |MariaDB|.
107
108+ * :rn:`5.6.15-63.0`
109+ Default value for :variable:`thread_pool_max_threads` was changed from ``500`` to ``100 000``. This change was introduced because limiting the total number of threads in the :ref:`threadpool` can result in deadlocks and uneven distribution of worker threads between thread groups in case of stalled connections.
110+
111+ * :rn:`5.6.15-63.0`
112+ Default value for :variable:`thread_pool_high_prio_tickets` was changed from ``0`` to ``4294967295`` to enable the priority connection scheduling by default.
113+
114+ * :rn:`5.6.15-63.0`
115+ Implemented new :variable:`thread_pool_high_prio_mode` variable.
116+
117+ * :rn:`5.6.15-63.0`
118+ Implemented :ref:`low_priority_queue_throttling`.
119+
120+ * :rn:`5.6.15-63.0`
121+ Ported |MariaDB| patch `MDEV-156 <https://mariadb.atlassian.net/browse/MDEV-156>`_ to improve Thread Pool behavior when network wait times are not insignificant.
122+
123 System Variables
124 ================
125
126@@ -66,16 +101,36 @@
127
128 This variable can be used to limit the time an idle thread should wait before exiting.
129
130+.. variable:: thread_pool_high_prio_mode
131+
132+ :cli: Yes
133+ :conf: Yes
134+ :scope: Global, Session
135+ :dyn: Yes
136+ :vartype: String
137+ :default: ``transactions``
138+ :allowed: ``transactions``, ``statements``, ``none``
139+
140+This variable is used to provide more fine-grained control over high priority scheduling either globally or per connection.
141+
142+The following values are allowed:
143+
144+ * ``transactions`` (the default). In this mode only statements from already started transactions may go into the high priority queue depending on the number of high priority tickets currently available in a connection (see :variable:`thread_pool_high_prio_tickets`).
145+
146+ * ``statements``. In this mode all individual statements go into the high priority queue, regardless of connection's transactional state and the number of available high priority tickets. This value can be used to prioritize ``AUTOCOMMIT`` transactions or other kinds of statements such as administrative ones for specific connections. Note that setting this value globally essentially disables high priority scheduling, since in this case all statements from all connections will use a single queue (the high priority one)
147+
148+ * ``none``. This mode disables high priority queue for a connection. Some connections (e.g. monitoring) may be insensitive to execution latency and/or never allocate any server resources that would otherwise impact performance in other connections and thus, do not really require high priority scheduling. Note that setting :variable:`thread_pool_high_prio_mode` to ``none`` globally has essentially the same effect as setting it to ``statements`` globally: all connections will always use a single queue (the low priority one in this case).
149+
150 .. variable:: thread_pool_high_prio_tickets
151
152 :cli: Yes
153 :conf: Yes
154- :scope: Global
155+ :scope: Global, Session
156 :dyn: Yes
157 :vartype: Numeric
158- :default: 0
159+ :default: 4294967295
160
161-This variable controls the high priority queue policy. Each new connection is assigned this many tickets to enter the high priority queue.
162+This variable controls the high priority queue policy. Each new connection is assigned this many tickets to enter the high priority queue. Setting this variable to ``0`` will disable the high priority queue.
163
164 .. variable:: thread_pool_max_threads
165
166@@ -84,7 +139,7 @@
167 :scope: Global
168 :dyn: Yes
169 :vartype: Numeric
170- :default: 500
171+ :default: 100000
172
173 This variable can be used to limit the maximum number of threads in the pool. Once this number is reached no new threads will be created.
174
175
176=== modified file 'doc/source/ps-versions-comparison.rst'
177--- doc/source/ps-versions-comparison.rst 2013-11-29 07:32:29 +0000
178+++ doc/source/ps-versions-comparison.rst 2013-12-19 13:41:48 +0000
179@@ -208,6 +208,9 @@
180 * - Feature not implemented
181 - Feature not implemented
182 - :ref:`Per-query variable statement <ps56:per_query_variable_statement>`
183+ * - Feature not implemented
184+ - :ref:`Extended mysqlbinlog <ps55:extended_mysqlbinlog>`
185+ - :ref:`Extended mysqlbinlog <ps56:extended_mysqlbinlog>`
186
187
188 Other Reading
189
190=== added file 'doc/source/release-notes/Percona-Server-5.6.15-63.0.rst'
191--- doc/source/release-notes/Percona-Server-5.6.15-63.0.rst 1970-01-01 00:00:00 +0000
192+++ doc/source/release-notes/Percona-Server-5.6.15-63.0.rst 2013-12-19 13:41:48 +0000
193@@ -0,0 +1,53 @@
194+.. rn:: 5.6.15-63.0
195+
196+==============================
197+ |Percona Server| 5.6.15-63.0
198+==============================
199+
200+Percona is glad to announce the release of |Percona Server| 5.6.15-63.0 on December 19th, 2013 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.15-63.0/>`_ and from the :doc:`Percona Software Repositories </installation>`.
201+
202+Based on `MySQL 5.6.15 <http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-15.html>`_, including all the bug fixes in it, |Percona Server| 5.6.15-63.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.15-63.0 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.6.15-63.0>`_.
203+
204+New Features
205+============
206+
207+ :ref:`threadpool` high priority scheduling is now enabled by default by changing the default :variable:`thread_pool_high_prio_tickets` value from ``0`` to ``4294967295``.
208+
209+ |Percona Server| now supports :ref:`low_priority_queue_throttling`. This feature should improve :ref:`threadpool` performance under high concurrency in a situation when thread groups are oversubscribed.
210+
211+ Introduced new :variable:`thread_pool_high_prio_mode` to provide more fine-grained control over high priority scheduling either globally or per connection in :ref:`threadpool`.
212+
213+ |Percona Server| has :ref:`extended <extended_mysqlbinlog>` :command:`mysqlbinlog` to provide ``SSL`` and compression support.
214+
215+ |Percona Server| has reduced the performance overhead of the :ref:`user_stats` feature.
216+
217+Bugs Fixed
218+==========
219+
220+ ``INSTALL PLUGIN`` statement would crash server if :ref:`user_stats` were enabled. Bug fixed :bug:`1011047`.
221+
222+ :variable:`innodb_log_checksum_algorithm` did not have any effect when set from :file:`my.cnf` or mysqld command line, it would have effect only if set dynamically. Bug fixed :bug:`1248505`.
223+
224+ Server would crash on shutdown if :ref:`atomic_fio` feature is enabled. Bug fixed :bug:`1255628` (*Jan Lindström*).
225+
226+ |Percona Server| would crash when data was select from :table:`XTRADB_RSEG` table when |InnoDB| system table space was initialized with lower then default number of rollback segments. Bug fixed :bug:`1260259`.
227+
228+ Certain types of workloads (large result sets, blobs, slow clients) can have longer waits on network I/O (socket reads and writes). Whenever server waits, this should be communicated to the :ref:`threadpool`, so it can start new query by either waking a waiting thread or sometimes creating a new one. Ported |MariaDB| patch `MDEV-156 <https://mariadb.atlassian.net/browse/MDEV-156>`_, bug fixed :bug:`1159743`.
229+
230+ ``mysqldump --innodb-optimize-keys`` was generating incorrect ``CREATE TABLE`` statements for partitioned tables. Bug fixed :bug:`1233841`.
231+
232+ Fixed errors when server was compiled with ``-DWITH_LIBWRAP=ON`` option. Bug fixed :bug:`1240442`.
233+
234+ If :variable:`innobase_atomic_writes` was used on separate undo files that do not exists would lead to operating system error. Bug fixed :bug:`1255638` (*Jan Lindström*).
235+
236+ Default value for :variable:`thread_pool_max_threads` has been changed from ``500`` to ``100 000`` (the maximum supported number of connections), because limiting the total number of threads in the :ref:`threadpool` can result in deadlocks and uneven distribution of worker threads between thread groups in case of stalled connections. Bug fixed :bug:`1258097`.
237+
238+ ``PURGE CHANGED_PAGE_BITMAPS BEFORE`` statement would delete the changed page data after the specified LSN and up to the start of the next bitmap file. If this data were to be used for fast incremental backups, its absence would cause |Percona XtraBackup| to fall back to the full-scan incremental backup mode. Bug fixed :bug:`1260035` (*Andrew Gaul*).
239+
240+ Server performance could degrade under heavy load or it could deadlock on shutdown while performing purge. Bug fixed :bug:`1236696`.
241+
242+ Server could crash under heavy load if |InnoDB| compression was used. Bug fixed :bug:`1240371`.
243+
244+ Redo log checksum mismatches would be diagnosed using the data page checksum algorithm setting instead of redo log checksum algorithm one. Bug fixed :bug:`1250148`.
245+
246+Other bugs fixed: bug :bug:`1082333`, bug :bug:`1260945`, bug :bug:`1248046`, bug :bug:`1243067`, bug :bug:`1238563`, bug :bug:`1258154` (upstream bug :mysqlbug:`71092`), bug :bug:`1242748`, bug :bug:`1239062`, bug :bug:`1200788`, bug :bug:`1193319`, bug :bug:`1240044`.
247
248=== modified file 'doc/source/release-notes/release-notes_index.rst'
249--- doc/source/release-notes/release-notes_index.rst 2013-12-16 08:45:31 +0000
250+++ doc/source/release-notes/release-notes_index.rst 2013-12-19 13:41:48 +0000
251@@ -6,6 +6,7 @@
252 :maxdepth: 1
253 :glob:
254
255+ Percona-Server-5.6.15-63.0
256 Percona-Server-5.6.14-62.0
257 Percona-Server-5.6.13-61.0
258 Percona-Server-5.6.13-60.6
259
260=== modified file 'doc/source/upgrading_guide_55_56.rst'
261--- doc/source/upgrading_guide_55_56.rst 2013-05-10 13:29:38 +0000
262+++ doc/source/upgrading_guide_55_56.rst 2013-12-19 13:41:48 +0000
263@@ -1,8 +1,8 @@
264 .. _upgrading_guide:
265
266-=========================================================
267- Percona Sever In-Place Upgrading Guide: From 5.5 to 5.6
268-=========================================================
269+==========================================================
270+ Percona Server In-Place Upgrading Guide: From 5.5 to 5.6
271+==========================================================
272
273 In-place upgrades are those which are done using the existing data in the server. Generally speaking, this is stopping the server, installing the new server and starting it with the same data files. While they may not be suitable for high-complexity environments, they may be adequate for many scenarios.
274
275
276=== modified file 'doc/source/upstream-bug-fixes.rst'
277--- doc/source/upstream-bug-fixes.rst 2013-10-23 08:48:28 +0000
278+++ doc/source/upstream-bug-fixes.rst 2013-12-19 13:41:48 +0000
279@@ -5,27 +5,39 @@
280 =============================================================
281
282 +-------------------------------------------------------------------------------------------------------------+
283+|:Upstream bug: :mysqlbug:`41975` - Support for SSL options not included in mysqlbinlog |
284+|:Launchpad bug: :bug:`1258154` |
285+|:Upstream state: Closed |
286+|:Fix Released: :rn:`5.6.15-63.0` |
287+|:Upstream fix: N/A |
288++-------------------------------------------------------------------------------------------------------------+
289+|:Upstream bug: :mysqlbug:`71092` - InnoDB FTS introduced new mutex sync level in 5.6.15, broke UNIV_SYNC ... |
290+|:Launchpad bug: :bug:`1258154` |
291+|:Upstream state: Verified (checked on 2013-12-19) |
292+|:Fix Released: :rn:`5.6.15-63.0` |
293+|:Upstream fix: N/A |
294++-------------------------------------------------------------------------------------------------------------+
295 |:Upstream bug: :mysqlbug:`70417` - rw_lock_x_lock_func_nowait() calls os_thread_get_curr_id() mostly ... |
296 |:Launchpad bug: :bug:`1230220` |
297-|:Upstream state: Verified (checked on 2013-10-09) |
298+|:Upstream state: Closed |
299 |:Fix Released: :rn:`5.6.13-61.0` |
300-|:Upstream fix: N/A |
301+|:Upstream fix: 5.6.16 |
302 +-------------------------------------------------------------------------------------------------------------+
303 |:Upstream bug: :mysqlbug:`70490` - Suppression is too strict on some systems |
304 |:Launchpad bug: :bug:`1205196` |
305-|:Upstream state: Need Feedback (checked on 2013-10-09) |
306+|:Upstream state: No Feedback (checked on 2013-12-19) |
307 |:Fix Released: :rn:`5.6.13-61.0` |
308 |:Upstream fix: N/A |
309 +-------------------------------------------------------------------------------------------------------------+
310 |:Upstream bug: :mysqlbug:`64556` - Interrupting a query inside InnoDB causes an unrelated warning to be ... |
311 |:Launchpad bug: :bug:`1115158` |
312-|:Upstream state: Verified (checked on 2013-10-09) |
313+|:Upstream state: Verified (checked on 2013-12-19) |
314 |:Fix Released: :rn:`5.6.13-61.0` |
315 |:Upstream fix: N/A |
316 +-------------------------------------------------------------------------------------------------------------+
317 |:Upstream bug: :mysqlbug:`70500` - Page cleaner should perform LRU flushing regardless of server activity |
318 |:Launchpad bug: :bug:`1234562` |
319-|:Upstream state: Open (checked on 2013-10-09) |
320+|:Upstream state: Open (checked on 2013-12-19) |
321 |:Fix Released: :rn:`5.6.13-61.0` |
322 |:Upstream fix: N/A |
323 +-------------------------------------------------------------------------------------------------------------+
324@@ -37,45 +49,45 @@
325 +-------------------------------------------------------------------------------------------------------------+
326 |:Upstream bug: :mysqlbug:`70489` - Crash when using AES_ENCRYPT on empty string |
327 |:Launchpad bug: :bug:`1201033` |
328-|:Upstream state: Open (checked on 2013-10-09) |
329+|:Upstream state: Unsupported |
330 |:Fix Released: :rn:`5.6.13-61.0` |
331 |:Upstream fix: N/A |
332 +-------------------------------------------------------------------------------------------------------------+
333 |:Upstream bug: :mysqlbug:`68481` - InnoDB LRU flushing for MySQL 5.6 needs work |
334 |:Launchpad bug: :bug:`1232406` |
335-|:Upstream state: Verified (checked on 2013-10-09) |
336+|:Upstream state: Verified (checked on 2013-12-19) |
337 |:Fix Released: :rn:`5.6.13-61.0` |
338 |:Upstream fix: N/A |
339 +-------------------------------------------------------------------------------------------------------------+
340 |:Upstream bug: :mysqlbug:`70453` - Add hard timeouts to page cleaner flushes |
341 |:Launchpad bug: :bug:`1232101` |
342-|:Upstream state: Verified (checked on 2013-10-09) |
343+|:Upstream state: Verified (checked on 2013-12-19) |
344 |:Fix Released: :rn:`5.6.13-61.0` |
345 |:Upstream fix: N/A |
346 +-------------------------------------------------------------------------------------------------------------+
347 |:Upstream bug: :mysqlbug:`69170` - buf_flush_LRU is lazy |
348 |:Launchpad bug: :bug:`1231918` |
349-|:Upstream state: Verified (checked on 2013-10-09) |
350+|:Upstream state: Verified (checked on 2013-12-19) |
351 |:Fix Released: :rn:`5.6.13-61.0` |
352 |:Upstream fix: N/A |
353 +-------------------------------------------------------------------------------------------------------------+
354 |:Upstream bug: :mysqlbug:`68555` - thread convoys from log_checkpoint_margin with innodb_buffer_pool_inst... |
355 |:Launchpad bug: :bug:`1236884` |
356-|:Upstream state: Verified (checked on 2013-10-09) |
357+|:Upstream state: Verified (checked on 2013-12-19) |
358 |:Fix Released: :rn:`5.6.13-61.0` |
359 |:Upstream fix: N/A |
360 +-------------------------------------------------------------------------------------------------------------+
361 |:Upstream bug: :mysqlbug:`70228` - Is buf_LRU_free_page() really supposed to make non-zip block sticky at ...|
362 |:Launchpad bug: :bug:`1220544` |
363-|:Upstream state: Verified (checked on 2013-10-09) |
364+|:Upstream state: Verified (checked on 2013-12-19) |
365 |:Fix Released: :rn:`5.6.13-60.6` |
366 |:Upstream fix: N/A |
367 +-------------------------------------------------------------------------------------------------------------+
368 |:Upstream bug: :mysqlbug:`69617` - 5.6.12 removed UNIV_SYNC_DEBUG from UNIV_DEBUG |
369 |:Launchpad bug: :bug:`1216815` |
370-|:Upstream state: Verified (checked on 2013-10-09) |
371+|:Upstream state: Closed |
372 |:Fix Released: :rn:`5.6.13-60.6` |
373-|:Upstream fix: N/A |
374+|:Upstream fix: 5.6.16 |
375 +-------------------------------------------------------------------------------------------------------------+
376 |:Upstream bug: :mysqlbug:`69258` - does buf_LRU_buf_pool_running_out need to lock buffer pool mutexes |
377 |:Launchpad bug: :bug:`1219842` |
378@@ -85,13 +97,13 @@
379 +-------------------------------------------------------------------------------------------------------------+
380 |:Upstream bug: :mysqlbug:`70216` - Unnecessary overhead from persistent adaptive hash index latches |
381 |:Launchpad bug: :bug:`1218347` |
382-|:Upstream state: Verified (checked on 2013-10-09) |
383+|:Upstream state: Verified (checked on 2013-12-19) |
384 |:Fix Released: :rn:`5.6.13-60.6` |
385 |:Upstream fix: N/A |
386 +-------------------------------------------------------------------------------------------------------------+
387 |:Upstream bug: :mysqlbug:`62018` - innodb adaptive hash index mutex contention |
388 |:Launchpad bug: :bug:`1216804` |
389-|:Upstream state: Verified (checked on 2013-10-09) |
390+|:Upstream state: Verified (checked on 2013-12-19) |
391 |:Fix Released: :rn:`5.6.13-60.6` |
392 |:Upstream fix: N/A |
393 +-------------------------------------------------------------------------------------------------------------+
394@@ -103,13 +115,13 @@
395 +-------------------------------------------------------------------------------------------------------------+
396 |:Upstream bug: :mysqlbug:`42415` - UPDATE/DELETE with LIMIT clause unsafe for SBL even with ORDER BY PK ... |
397 |:Launchpad bug: :bug:`1132194` |
398-|:Upstream state: Verified (checked on 2013-10-09) |
399+|:Upstream state: Verified (checked on 2013-12-19) |
400 |:Fix Released: :rn:`5.6.13-60.5` |
401 |:Upstream fix: N/A |
402 +-------------------------------------------------------------------------------------------------------------+
403 |:Upstream bug: :mysqlbug:`69639` - mysql failed to build with dtrace Sun D 1.11 |
404 |:Launchpad bug: :bug:`1196460` |
405-|:Upstream state: Open (checked on 2013-10-09) |
406+|:Upstream state: Open (checked on 2013-12-19) |
407 |:Fix Released: :rn:`5.6.13-60.5` |
408 |:Upstream fix: N/A |
409 +-------------------------------------------------------------------------------------------------------------+
410@@ -127,19 +139,25 @@
411 +-------------------------------------------------------------------------------------------------------------+
412 |:Upstream bug: :mysqlbug:`69856` - mysql_install_db does not function properly in 5.6 for debug builds |
413 |:Launchpad bug: :bug:`1179359` |
414-|:Upstream state: Verified (checked on 2013-10-09) |
415+|:Upstream state: Verified (checked on 2013-12-19) |
416 |:Fix Released: :rn:`5.6.12-60.4` |
417 |:Upstream fix: N/A |
418 +-------------------------------------------------------------------------------------------------------------+
419+|:Upstream bug: :mysqlbug:`63451` - atomic/x86-gcc.h:make_atomic_cas_body64 potential miscompilation bug |
420+|:Launchpad bug: :bug:`878022` |
421+|:Upstream state: Closed |
422+|:Fix Released: :rn:`5.6.11-60.3` |
423+|:Upstream fix: 5.6.16 |
424++-------------------------------------------------------------------------------------------------------------+
425 |:Upstream bug: :mysqlbug:`70277` - last argument of LOAD DATA ... SET ... statement repeated twice in binlog |
426 |:Launchpad bug: :bug:`1223196` |
427-|:Upstream state: Verified (checked on 2013-10-09) |
428+|:Upstream state: Closed |
429 |:Fix Released: :rn:`5.6.11-60.3` |
430-|:Upstream fix: N/A |
431+|:Upstream fix: 5.6.15 |
432 +-------------------------------------------------------------------------------------------------------------+
433 |:Upstream bug: :mysqlbug:`69252` - All the parts.partition_max* tests are broken with MTR --parallel |
434 |:Launchpad bug: :bug:`1180481` |
435-|:Upstream state: Verified (checked on 2013-10-09) |
436+|:Upstream state: Verified (checked on 2013-12-19) |
437 |:Fix Released: :rn:`5.6.11-60.3` |
438 |:Upstream fix: N/A |
439 +-------------------------------------------------------------------------------------------------------------+
440@@ -151,7 +169,7 @@
441 +-------------------------------------------------------------------------------------------------------------+
442 |:Upstream bug: :mysqlbug:`68714` - Remove literal statement digest values from perfschema tests |
443 |:Launchpad bug: :bug:`1157078` |
444-|:Upstream state: Verified (checked on 2013-10-09) |
445+|:Upstream state: Verified (checked on 2013-12-19) |
446 |:Fix Released: :rn:`5.6.11-60.3` |
447 |:Upstream fix: N/A |
448 +-------------------------------------------------------------------------------------------------------------+
449@@ -175,13 +193,13 @@
450 +-------------------------------------------------------------------------------------------------------------+
451 |:Upstream bug: :mysqlbug:`68970` - fsp_reserve_free_extents switches from small to big tblspace handling ... |
452 |:Launchpad bug: :bug:`1169494` |
453-|:Upstream state: Verified (checked on 2013-10-09) |
454+|:Upstream state: Verified (checked on 2013-12-19) |
455 |:Fix Released: :rn:`5.6.11-60.3` |
456 |:Upstream fix: N/A |
457 +-------------------------------------------------------------------------------------------------------------+
458 |:Upstream bug: :mysqlbug:`68713` - create_duplicate_weedout_tmp_table() leaves key_part_flag uninitialized |
459 |:Launchpad bug: :bug:`1157037` |
460-|:Upstream state: Verified (checked on 2013-10-09) |
461+|:Upstream state: Verified (checked on 2013-12-19) |
462 |:Fix Released: :rn:`5.6.11-60.3` |
463 |:Upstream fix: N/A |
464 +-------------------------------------------------------------------------------------------------------------+
465@@ -193,13 +211,13 @@
466 +-------------------------------------------------------------------------------------------------------------+
467 |:Upstream bug: :mysqlbug:`68999` - SSL_OP_NO_COMPRESSION not defined |
468 |:Launchpad bug: :bug:`1183610` |
469-|:Upstream state: No Feedback (checked on 2013-10-09) |
470+|:Upstream state: No Feedback (checked on 2013-12-19) |
471 |:Fix Released: :rn:`5.6.11-60.3` |
472 |:Upstream fix: N/A |
473 +-------------------------------------------------------------------------------------------------------------+
474 |:Upstream bug: :mysqlbug:`68845` - Unnecessary log_sys->mutex reacquisition in mtr_log_reserve_and_write() |
475 |:Launchpad bug: :bug:`1163439` |
476-|:Upstream state: Verified (checked on 2013-10-09) |
477+|:Upstream state: Verified (checked on 2013-12-19) |
478 |:Fix Released: :rn:`5.6.11-60.3` |
479 |:Upstream fix: N/A |
480 +-------------------------------------------------------------------------------------------------------------+
481@@ -229,7 +247,7 @@
482 +-------------------------------------------------------------------------------------------------------------+
483 |:Upstream bug: :mysqlbug:`68476` - Suboptimal code in my_strnxfrm_simple() |
484 |:Launchpad bug: :bug:`1132350` |
485-|:Upstream state: Verified (checked on 2013-10-09) |
486+|:Upstream state: Verified (checked on 2013-12-19) |
487 |:Fix Released: :rn:`5.6.11-60.3` |
488 |:Upstream fix: N/A |
489 +-------------------------------------------------------------------------------------------------------------+
490@@ -283,13 +301,13 @@
491 +-------------------------------------------------------------------------------------------------------------+
492 |:Upstream bug: :mysqlbug:`61180` - korr/store macros in my_global.h assume the argument to be a char pointer |
493 |:Launchpad bug: :bug:`1042517` |
494-|:Upstream state: Verified (checked on 2013-10-09) |
495+|:Upstream state: Verified (checked on 2013-12-19) |
496 |:Fix Released: :rn:`5.6.11-60.3` |
497 |:Upstream fix: N/A |
498 +-------------------------------------------------------------------------------------------------------------+
499 |:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|
500 |:Launchpad bug: :bug:`1042517` |
501-|:Upstream state: Verified (checked on 2013-10-09) |
502+|:Upstream state: Verified (checked on 2013-12-19) |
503 |:Fix Released: :rn:`5.6.11-60.3` |
504 |:Upstream fix: N/A |
505 +-------------------------------------------------------------------------------------------------------------+
506@@ -301,7 +319,7 @@
507 +-------------------------------------------------------------------------------------------------------------+
508 |:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no. |
509 |:Launchpad bug: :bug:`1013432` |
510-|:Upstream state: Verified (checked on 2013-10-09) |
511+|:Upstream state: Verified (checked on 2013-12-19) |
512 |:Fix Released: :rn:`5.6.11-60.3` |
513 |:Upstream fix: N/A |
514 +-------------------------------------------------------------------------------------------------------------+
515@@ -331,13 +349,13 @@
516 +-------------------------------------------------------------------------------------------------------------+
517 |:Upstream bug: :mysqlbug:`25007` - memory tables with dynamic rows format |
518 |:Launchpad bug: N/A |
519-|:Upstream state: Verified (checked on 2013-10-09) |
520+|:Upstream state: Verified (checked on 2013-12-19) |
521 |:Fix Released: :rn:`5.6.11-60.3` |
522 |:Upstream fix: N/A |
523 +-------------------------------------------------------------------------------------------------------------+
524 |:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |
525 |:Launchpad bug: :bug:`800035` |
526-|:Upstream state: Verified (checked on 2013-10-09) |
527+|:Upstream state: Verified (checked on 2013-12-19) |
528 |:Fix Released: :rn:`5.6.11-60.3` |
529 |:Upstream fix: N/A |
530 +-------------------------------------------------------------------------------------------------------------+
531@@ -349,25 +367,25 @@
532 +-------------------------------------------------------------------------------------------------------------+
533 |:Upstream bug: :mysqlbug:`68116` - InnoDB monitor may hit an assertion error in buf_page_get_gen in debug ...|
534 |:Launchpad bug: :bug:`1100178` |
535-|:Upstream state: Analyzing (checked on 2013-10-09) |
536+|:Upstream state: Analyzing (checked on 2013-12-19) |
537 |:Fix Released: :rn:`5.6.10-60.2` |
538 |:Upstream fix: N/A |
539 +-------------------------------------------------------------------------------------------------------------+
540 |:Upstream bug: :mysqlbug:`65946` - Sid_map::Sid_map calls DBUG which may have unitialized THR_KEY_mysys and..|
541 |:Launchpad bug: :bug:`1050758` |
542-|:Upstream state: Duplicate |
543+|:Upstream state: Duplicate/Closed |
544 |:Fix Released: :rn:`5.6.5-60.0` |
545-|:Upstream fix: N/A |
546+|:Upstream fix: 5.6.15 |
547 +-------------------------------------------------------------------------------------------------------------+
548 |:Upstream bug: :mysqlbug:`20001` - Support for temp-tables in INFORMATION_SCHEMA |
549 |:Launchpad bug: N/A |
550-|:Upstream state: Verified (checked on 2013-10-09) |
551+|:Upstream state: Verified (checked on 2013-12-19) |
552 |:Fix Released: :rn:`5.6.5-60.0` |
553 |:Upstream fix: N/A |
554 +-------------------------------------------------------------------------------------------------------------+
555 |:Upstream bug: :mysqlbug:`69146` - Optimization in buf_pool_get_oldest_modification if srv_buf_pool_instances|
556 |:Launchpad bug: :bug:`1176496` |
557-|:Upstream state: Open (checked on 2013-10-09) |
558+|:Upstream state: Open (checked on 2013-12-19) |
559 |:Fix Released: :rn:`5.6.5-60.0` |
560 |:Upstream fix: N/A |
561 +-------------------------------------------------------------------------------------------------------------+

Subscribers

People subscribed via source and target branches