Merge lp:~hrvojem/percona-server/rn-5.5.36-34.0-5.6 into lp:percona-server/5.6

[Hrvoje Matijakovic]

[Alexey Kopytov (akopytov)]

Where did the "Lightweight Locks" name come from? The feature is called backup locks in the blueprint.

[Hrvoje Matijakovic (hrvojem)]

> Where did the "Lightweight Locks" name come from? The feature is called backup
> locks in the blueprint.

BP says:
Add functionality to Percona Server and XtraBackup to support lightweight locks

[Hrvoje Matijakovic (hrvojem)]

> Where did the "Lightweight Locks" name come from? The feature is called backup
> locks in the blueprint.

Wrong BP in the last one, it should be:

Add functionality to Percona Server lightweight locks

[Alexey Kopytov (akopytov)]

Hrvoje,

OK, I see. The feature has been renamed twice since the BP was created. Let's keep the "backup locks" name, as it is more explicit IMO.

review: Needs Fixing

[Hrvoje Matijakovic (hrvojem)]

> Hrvoje,
>
> OK, I see. The feature has been renamed twice since the BP was created. Let's
> keep the "backup locks" name, as it is more explicit IMO.

Ah, should be fixed now

[Laurynas Biveinis (laurynas-biveinis)]

    - 50: s/5.5/5.6
    - 142: s/another MDL lock type/another new MDL lock type
    - 252: "XtraDB utility thread" is too generic thread name (and
      incorrect: master, purge, cleaner threads are already
      collectively "InnoDB utility threads"). The fitting name could
      be either "LRU cleaner thread", either, as it is called in the
      code, "LRU manager thread". (it is called this way because there
      are plans to extend it to perform more than LRU flushing in the
      future). Please rename the rst file too.
    - 255 and a corresponding part in RN: s/has implemented a new
      .../has split a new ... out of the InnoDB cleaner thread
    - Remove 262, it is invalidated by upstream 5.6.16.
    - s/free lists/buffer pool free lists/g
    - The existing innodb_sched_priority_cleaner and
      innodb_priority_cleaner docs must be updated to indicate that
      they apply to the LRU manager
      too. innodb_sched_priority_cleaner docs are duplicated.
    - 342: FLUSH STATUS could cause a server crash on the next
      transaction commit if two XA-supporting storage engines are in
      use.
    - 358: "The fix for upstream bug ... Bug fixed :bug:`1279671`
      (upstream ... )" (yes this is different from my previous
      suggestion; sorry about that).
    - I don't see the "Percona Server source layout now matches MySQL
      layout better", which should be the same as in 5.5?
    - 1264952 needs description

review: Needs Fixing

[Hrvoje Matijakovic (hrvojem)]

> - The existing innodb_sched_priority_cleaner and
> innodb_priority_cleaner docs must be updated to indicate that
> they apply to the LRU manager
> too. innodb_sched_priority_cleaner docs are duplicated.

Fixed everything except this.

[Laurynas Biveinis (laurynas-biveinis)]

    - 257: s/thread/threads
    - 259: s/page cleaner/LRU manager
    - 263: s/mutex contentions, as the buffer pool free list
      mutex/buffer pool free list mutex contention, as the mutex
    - 263: s/was/is
    - 263: s/to the page cleaner thread/to the LRU manager thread
    - 276: s/cleaner/page cleaner
    - 316: s/LRU list/buffer pool LRU list
    - 316: s/buffer pool free lists/buffer pool free list
    - 325: s/cleaner and LRU manager priority thread/page cleaner and
      LRU manager threads
    - 378: s/an alternative/a lightweight alternative, s/for taking
      backups/for taking physical and logical backups
    - 433: Performance schema autosizing heuristics have been updated
      to account for Percona Server-specific
      wait/synch/mutex/sql/THD::LOCK_temporary_tables mutex.

review: Needs Fixing

[Laurynas Biveinis (laurynas-biveinis)]

    - 263: s/by query thread/by a query thread
    - 276: no need to link to cleaner page tuning here?

review: Needs Fixing

[Laurynas Biveinis (laurynas-biveinis)]

https://bugs.launchpad.net/percona-server/+bug/1238039 now has an upstream bug http://bugs.mysql.com/bug.php?id=71988

review: Needs Fixing

[Laurynas Biveinis (laurynas-biveinis)]

review: Approve

=== modified file 'doc/source/conf.py'
--- doc/source/conf.py	2014-03-04 06:02:56 +0000
+++ doc/source/conf.py	2014-03-10 15:06:07 +0000
@@ -54,7 +54,7 @@
 # The short X.Y version.
 version = '5.6'
 # The full version, including alpha/beta/rc tags.
-release = '5.6.16-64.0-tokudb'
+release = '5.6.16-64.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

=== modified file 'doc/source/flexibility/mysqlbinlog_change_db.rst'
--- doc/source/flexibility/mysqlbinlog_change_db.rst	2014-03-03 18:32:52 +0000
+++ doc/source/flexibility/mysqlbinlog_change_db.rst	2014-03-10 15:06:07 +0000
@@ -32,7 +32,7 @@
  COMMIT/*!*/;
  DELIMITER ;
 
-**mysqlbinlog** output when the new variable is used:  :: 
+**mysqlbinlog** output when the new option is used:  :: 
 
  $ mysqlbinlog --rewrite-db='world->new_world' mysql-bin.000005
  ...
@@ -67,7 +67,7 @@
 ============================
 
   * :rn:`5.6.16-64.0`
-    Feature ported from |Percona Server| 5.1
+    Full functionality.
 
 Client Command Line Parameter
 =============================

=== added file 'doc/source/flexibility/slowlog_rotation.rst'
--- doc/source/flexibility/slowlog_rotation.rst	1970-01-01 00:00:00 +0000
+++ doc/source/flexibility/slowlog_rotation.rst	2014-03-10 15:06:07 +0000
@@ -0,0 +1,53 @@
+.. _slowlog_rotation:
+
+========================================
+ Slow Query Log Rotation and Expiration
+========================================
+
+.. note:: 
+
+   This feature is currently considered BETA quality.
+
+Percona has implemented two new variables, :variable:`max_slowlog_size` and :variable:`max_slowlog_files` to provide users with ability to control the slow query log disk usage. These variables have the same behavior as upstream variable `max_binlog_size <https://dev.mysql.com/doc/refman/5.6/en/replication-options-binary-log.html#sysvar_max_binlog_size>`_ and :variable:`max_binlog_files` variable used for controlling the binary log.
+
+.. warning::
+
+   For this feature to work variable :variable:`slow_query_log_file` needs to be set up manually and without the ``.log`` sufix. The slow query log files will be named using :variable:`slow_query_log_file` as a stem, to which a dot and a sequence number will be appended.
+
+Version Specific Information
+============================
+
+  * :rn:`5.6.16-64.0`:
+    Variable :variable:`max_slowlog_size` introduced.
+
+  * :rn:`5.6.16-64.0`:
+    Variable :variable:`max_slowlog_files` introduced.
+
+System Variables
+================
+
+.. variable:: max_slowlog_size
+
+     :version 5.6.16-64.0: Introduced.
+     :cli: Yes
+     :conf: Yes
+     :scope: Global
+     :dyn: Yes
+     :vartype: numeric
+     :default: 0 (unlimited)
+     :range: 4096 - 1073741824
+
+Slow query log will be rotated automatically when its size exceeds this value. The default is ``0``, don't limit the size. When this feature is enabled slow query log file will be renamed to :variable:`slow_query_log_file`.000001. 
+
+.. variable:: max_slowlog_files
+
+     :version 5.6.16-64.0: Introduced.
+     :cli: Yes
+     :conf: Yes
+     :scope: Global
+     :dyn: Yes
+     :vartype: numeric
+     :default: 0 (unlimited)
+     :range: 0 - 102400
+
+Maximum number of slow query log files. Used with :variable:`max_slowlog_size` this can be used to limit the total amount of slow query log files. When this number is reached server will create a new slow query log file with increased sequence number. Log file with the lowest sequence number will be deleted.

=== modified file 'doc/source/index.rst'
--- doc/source/index.rst	2014-03-04 06:02:56 +0000
+++ doc/source/index.rst	2014-03-10 15:06:07 +0000
@@ -89,6 +89,7 @@
    flexibility/extended_select_into_outfile
    flexibility/per_query_variable_statement
    flexibility/extended_mysqlbinlog
+   flexibility/slowlog_rotation
    flexibility/mysqlbinlog_change_db
 
 Reliability Improvements
@@ -122,6 +123,7 @@
    management/innodb_expanded_fast_index_creation
    management/log_archiving
    management/statement_timeout
+   management/backup_locks
 
 Diagnostics Improvements
 ========================

=== added file 'doc/source/management/backup_locks.rst'
--- doc/source/management/backup_locks.rst	1970-01-01 00:00:00 +0000
+++ doc/source/management/backup_locks.rst	2014-03-10 15:06:07 +0000
@@ -0,0 +1,124 @@
+.. _backup_locks:
+
+==============
+ Backup Locks
+==============
+
+|Percona Server| has implemented this feature in :rn:`5.6.16-64.0` to be a lightweight alternative to ``FLUSH TABLES WITH READ LOCK`` for both physical and logical backups. Three new statements are now available: ``LOCK TABLES FOR BACKUP``, ``LOCK BINLOG FOR BACKUP`` and ``UNLOCK BINLOG``.
+
+``LOCK TABLES FOR BACKUP``
+---------------------------
+
+``LOCK TABLES FOR BACKUP`` uses a new MDL lock type to block updates to non-transactional tables and DDL statements for all tables. More specifically, if there's an active ``LOCK TABLES FOR BACKUP`` lock, all DDL statements and all updates to MyISAM, CSV, MEMORY and ARCHIVE tables will be blocked in the ``Waiting for backup lock`` status as visible in ``PERFORMANCE_SCHEMA`` or ``PROCESSLIST``. ``SELECT`` queries for all tables and ``INSERT/REPLACE/UPDATE/DELETE`` against |InnoDB|, Blackhole and Federated tables are not affected by ``LOCK TABLES FOR BACKUP``. Blackhole tables obviously have no relevance for backups, and Federated tables are ignored by both logical and physical backup tools.
+
+Unlike ``FLUSH TABLES WITH READ LOCK``, ``LOCK TABLES FOR BACKUP`` does not flush tables, i.e. storage engines are not forced to close tables and tables are not expelled from the table cache. As a result, ``LOCK TABLES FOR BACKUP`` only waits for conflicting statements to complete (i.e. DDL and updates to non-transactional tables). It never waits for SELECTs, or UPDATEs to |InnoDB| tables to complete, for example.
+
+If an "unsafe" statement is executed in the same connection that is holding a ``LOCK TABLES FOR BACKUP`` lock, it fails with the following error: :: 
+
+ ERROR 1880 (HY000): Can't execute the query because you have a conflicting backup lock
+
+ UNLOCK TABLES releases the lock acquired by LOCK TABLES FOR BACKUP.
+
+``LOCK BINLOG FOR BACKUP``
+---------------------------
+
+``LOCK BINLOG FOR BACKUP`` uses another new MDL lock type to block all operations that might change either binary log position or ``Exec_Master_Log_Pos`` or ``Exec_Gtid_Set`` (i.e. master binary log coordinates corresponding to the current SQL thread state on a replication slave) as reported by ``SHOW MASTER``/``SLAVE STATUS``. More specifically, a commit will only be blocked if the binary log is enabled (both globally, and for connection with sql_log_bin), or if commit is performed by a slave thread and would advance ``Exec_Master_Log_Pos`` or ``Executed_Gtid_Set``. Connections that are currently blocked on the global binlog lock can be identified by the ``Waiting for binlog lock`` status in ``PROCESSLIST``.
+
+``UNLOCK BINLOG``
+------------------
+
+``UNLOCK BINLOG`` releases the ``LOCK BINLOG FOR BACKUP`` lock, if acquired by the current connection. The intended use case for |Percona XtraBackup| is: :: 
+
+  LOCK TABLES FOR BACKUP
+  ... copy .frm, MyISAM, CSV, etc. ...
+  LOCK BINLOG FOR BACKUP
+  UNLOCK TABLES
+  ... get binlog coordinates ...
+  ... wait for redo log copying to finish ...
+  UNLOCK BINLOG
+
+Privileges
+----------
+
+Both ``LOCK TABLES FOR BACKUP`` and ``LOCK BINLOG FOR BACKUP`` require the ``RELOAD`` privilege. The reason for that is to have the same requirements as ``FLUSH TABLES WITH READ LOCK``.
+
+Interaction with other global locks
+-----------------------------------
+
+Both ``LOCK TABLES FOR BACKUP`` and ``LOCK BINLOG FOR BACKUP`` have no effect if the current connection already owns a ``FLUSH TABLES WITH READ LOCK`` lock, as it's a more restrictive lock. If ``FLUSH TABLES WITH READ LOCK`` is executed in a connection that has acquired ``LOCK TABLES FOR BACKUP`` or ``LOCK BINLOG FOR BACKUP``, ``FLUSH TABLES WITH READ LOCK`` fails with an error.
+
+If the server is operating in the read-only mode (i.e. :variable:`read_only` set to ``1``), statements that are unsafe for backups will be either blocked or fail with an error, depending on whether they are executed in the same connection that owns ``LOCK TABLES FOR BACKUP`` lock, or other connections.
+
+MyISAM index and data buffering
+-------------------------------
+
+|MyISAM| key buffering is normally write-through, i.e. by the time each update to a |MyISAM| table is completed, all index updates are written to disk. The only exception is delayed key writing feature which is disabled by default. 
+
+When the global system variable :variable:`delay_key_write` is set to ``ALL``, key buffers for all |MyISAM| tables are not flushed between updates, so a physical backup of those tables may result in broken |MyISAM| indexes. To prevent this, ``LOCK TABLES FOR BACKUP`` will fail with an error if ``delay_key_write`` is set to ``ALL``. An attempt to set :variable:`delay_key_write` to ``ALL`` when there's an active backup lock will also fail with an error. 
+
+Another option to involve delayed key writing is to create |MyISAM| tables with the DELAY_KEY_WRITE option and set the :variable:`delay_key_write` variable to ``ON`` (which is the default). In this case, ``LOCK TABLES FOR BACKUP`` will not be able to prevent stale index files from appearing in the backup. Users are encouraged to set :variable:`delay_key_writes` to ``OFF`` in the configuration file, :file:`my.cnf`, or repair |MyISAM| indexes after restoring from a physical backup created with backup locks.
+
+|MyISAM| may also cache data for bulk inserts, e.g. when executing multi-row INSERTs or ``LOAD DATA`` statements. Those caches, however, are flushed between statements, so have no effect on physical backups as long as all statements updating |MyISAM| tables are blocked.
+
+mysqldump
+---------
+
+``mysqldump`` has also been extended with a new option, :option:`lock-for-backup` (disabled by default). When used together with the :option:`--single-transaction` option, the option makes ``mysqldump`` issue ``LOCK TABLES FOR BACKUP`` before starting the dump operation to prevent unsafe statements that would normally result in an inconsistent backup.
+
+When used without the :option:`single-transaction` option, :option:`lock-for-backup` is automatically converted to :option:`lock-all-tables`.
+
+Option :option:`lock-for-backup` is mutually exclusive with :option:`lock-all-tables`, i.e. specifying both on the command line will lead to an error. 
+
+If the backup locks feature is not supported by the target server, but :option:`lock-for-backup` is specified on the command line, ``mysqldump`` aborts with an error.
+
+If :option:`master-data` is used together with :option:`single-transaction`, :option:`lock-for-backup` does not have any effect, i.e. ``FLUSH TABLES WITH READ LOCK`` will still be used to get the binary log coordinates. This limitation will be removed after implementing the following `blueprint <https://blueprints.launchpad.net/percona-server/+spec/enhancements-for-start-transaction-with-consistent>`_.
+
+System Variables
+================
+
+.. variable:: have_backup_locks
+
+     :version 5.6.16-64.0: Implemented
+     :cli: Yes
+     :conf: No
+     :scope: Global
+     :dyn: No
+     :vartype: Boolean
+     :default: YES
+
+This is a server variable implemented to help other utilities decide what locking strategy can be implemented for a server. When available, the backup locks feature is supported by the server and the variable value is always ``YES``.
+
+Status Variables
+================
+
+.. variable:: Com_lock_tables_for_backup
+
+     :version 5.6.16-64.0: Implemented
+     :vartype: Numeric
+
+.. variable:: Com_lock_binlog_for_backup
+
+     :version 5.6.16-64.0: Implemented
+     :vartype: Numeric
+
+.. variable:: Com_unlock_binlog
+
+     :version 5.6.16-64.0: Implemented
+     :vartype: Numeric
+
+These status variables indicate the number of times the corresponding statements have been executed.
+
+Client Command Line Parameter
+=============================
+
+.. option:: lock-for-backup
+
+     :version 5.6.16-64.0: Implemented
+     :cli: Yes
+     :scope: Global
+     :dyn: No
+     :vartype: String
+     :default: Off
+
+When used together with the :option:`--single-transaction` option, the option makes ``mysqldump`` issue ``LOCK TABLES FOR BACKUP`` before starting the dump operation to prevent unsafe statements that would normally result in an inconsistent backup.
+

=== modified file 'doc/source/performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads.rst'
--- doc/source/performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads.rst	2013-10-24 09:04:33 +0000
+++ doc/source/performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads.rst	2014-03-10 15:06:07 +0000
@@ -12,13 +12,13 @@
 In highly-concurrent I/O-bound workloads the following situation may happen: 
 
  1) Buffer pool free lists are used faster than they are refilled by the LRU cleaner thread.
- 2) Buffer pool free lists become empty and more and more query and utility (i.e. purge) thread stall, checking whether a free list has became non-empty, sleeping, performing single-page LRU flushes.
- 3) The number of free list mutex waiters increases.
- 4) When the page cleaner thread (or a single page LRU flush by a query thread) finally produces a free page, it is starved from putting it on the free list as it must acquire the free list mutex too. However, being one thread in up to hundreds, the chances of a prompt acquisition are low.
-
-To avoid this |Percona Server| has implemented priority refill for the buffer pool free list in :rn:`5.6.13-61.0`. This implementation adjusts the free list producer to always acquire the mutex with high priority and free list consumer to always acquire the mutex with low priority. The implementation makes use of :ref:`thread priority lock framework <thread_priority>`.
-
-Even the above implementation does not fully resolve the mutex contentions, as the free list mutex is still being acquired needlessly whenever the free list is empty. This was addressed by delegating all the LRU flushes to the page cleaner thread, never attempting to evict a page or perform a LRU single page flush by query thread, and introducing a backoff algorithm to reduce free list mutex pressure on empty free lists. This is controlled through a new system variable :variable:`innodb_empty_free_list_algorithm`.
+ 2) Buffer pool free lists become empty and more and more query and utility (i.e. purge) threads stall, checking whether a buffer pool free list has became non-empty, sleeping, performing single-page LRU flushes.
+ 3) The number of buffer pool free list mutex waiters increases.
+ 4) When the LRU manager thread (or a single page LRU flush by a query thread) finally produces a free page, it is starved from putting it on the buffer pool free list as it must acquire the buffer pool free list mutex too. However, being one thread in up to hundreds, the chances of a prompt acquisition are low.
+
+To avoid this |Percona Server| has implemented priority refill for the buffer pool buffer pool free list in :rn:`5.6.13-61.0`. This implementation adjusts the buffer pool free list producer to always acquire the mutex with high priority and buffer pool free list consumer to always acquire the mutex with low priority. The implementation makes use of :ref:`thread priority lock framework <thread_priority>`.
+
+Even the above implementation does not fully resolve the buffer pool free list mutex contention, as the mutex is still being acquired needlessly whenever the buffer pool free list is empty. This is addressed by delegating all the LRU flushes to the to the LRU manager thread, never attempting to evict a page or perform a LRU single page flush by a query thread, and introducing a backoff algorithm to reduce buffer pool free list mutex pressure on empty buffer pool free lists. This is controlled through a new system variable :variable:`innodb_empty_free_list_algorithm`.
  
 .. variable:: innodb_empty_free_list_algorithm
 
@@ -32,6 +32,18 @@
 
 When ``legacy`` option is set, server will used the upstream algorithm and when the ``backoff`` is selected, |Percona| implementation will be used.
 
+.. _lru_manager_thread:
+
+LRU manager thread
+===================
+
+|Percona Server| :rn:`5.6.16-64.0` has split a new LRU manager thread out of the |InnoDB| page cleaner thread, that performs LRU flushes and evictions to refill the buffer pool free lists. Before this implementation this was done by the page_cleaner thread together with the flush list flushes.
+
+Downsides of that approach were: 
+
+ * The cleaner thread sleep time has to take into account both LRU and flush list needs, by using the shorter sleep time of the times requested by both. This meant that the code paths for the other one is called at times needlessly.
+ * LRU/flush list flushes in the cleaner are serialized, which may cause transient stalls (up to LRU/flush list flush timeout values, which are 1 second by default) for user threads in the cases of empty buffer pool free lists and large checkpoint age at the same time.
+
 Backoff for sync preflushes
 ===========================
 
@@ -71,7 +83,7 @@
    :values: 1-39
    :default: 19
 
-This variable is used to set a thread scheduling priority. Values correspond to  Linux ``nice`` values of ``-20..19``, where 0 is 19 (lowest priority) and 39 is -20 (highest priority).
+This variable is used to set a thread scheduling priority. Values correspond to  Linux ``nice`` values of ``-20..19``, where 0 is 19 (lowest priority) and 39 is -20 (highest priority). This priority value affects both cleaner and LRU manager threads.
 
 |Percona Server| has introduced several options, only available in builds compiled with ``UNIV_PERF_DEBUG`` C preprocessor define.
 
@@ -93,15 +105,6 @@
    :dyn: Yes
    :vartype: Boolean
 
-.. variable:: innodb_sched_priority_cleaner
-
-   :version 5.6.13-61.0: Introduced.
-   :cli: Yes
-   :conf: Yes
-   :scope: Global
-   :dyn: Yes
-   :vartype: Boolean
-
 .. variable:: innodb_sched_priority_master
  
    :version 5.6.13-61.0: Introduced.
@@ -116,7 +119,7 @@
 Thread Priority Locks
 =====================
 
-The |InnoDB| worker threads compete for the shared resource accesses with the query threads. Performance experiments show that under high concurrency the worker threads must acquire the shared resources with priority. To this end, a priority mutex and a priority RW lock locking primitives have been implemented, that use the existing sync array code to wake up any high-priority waiting threads before any low-priority waiting threads, as well as reduce any low-priority thread spinning if any high-priority waiters are already present for a given sync object. The following mutexes have been converted to be priority mutexes: dict_sys, LRU list, free list, rseg, log_sys, and internal hash table sync object array mutexes. The following RW locks have been converted to priority RW locks: fsp, page_hash, AHI, index, and purge. To specify which threads are high-priority for shared resource acquisition, |Percona Server| has introduced several tuning options, only available in builds compiled with ``UNIV_PERF_DEBUG`` C preprocessor define.
+The |InnoDB| worker threads compete for the shared resource accesses with the query threads. Performance experiments show that under high concurrency the worker threads must acquire the shared resources with priority. To this end, a priority mutex and a priority RW lock locking primitives have been implemented, that use the existing sync array code to wake up any high-priority waiting threads before any low-priority waiting threads, as well as reduce any low-priority thread spinning if any high-priority waiters are already present for a given sync object. The following mutexes have been converted to be priority mutexes: dict_sys, buffer pool LRU list, buffer pool free list, rseg, log_sys, and internal hash table sync object array mutexes. The following RW locks have been converted to priority RW locks: fsp, page_hash, AHI, index, and purge. To specify which threads are high-priority for shared resource acquisition, |Percona Server| has introduced several tuning options, only available in builds compiled with ``UNIV_PERF_DEBUG`` C preprocessor define.
 
 .. variable:: innodb_priority_purge
 
@@ -149,7 +152,7 @@
    :dyn: Yes
    :vartype: Boolean
 
-When this option is enabled buffer pool cleaner thread acquire shared resources with priority.
+When this option is enabled buffer pool page cleaner and LRU manager threads acquire shared resources with priority.
 
 .. variable:: innodb_priority_master
  

=== modified file 'doc/source/ps-versions-comparison.rst'
--- doc/source/ps-versions-comparison.rst	2014-03-03 18:32:52 +0000
+++ doc/source/ps-versions-comparison.rst	2014-03-10 15:06:07 +0000
@@ -45,7 +45,7 @@
      - Replaced by the upstream implementation [#n-4]_
    * - :ref:`Reduced Buffer Pool Mutex Contention <ps51:innodb_opt_lru_count>`
      - :ref:`Reduced Buffer Pool Mutex Contention <ps55:innodb_opt_lru_count>`
-     - Feature not implemented 
+     - Feature not implemented
    * - :ref:`InnoDB timer-based Concurrency Throttling <ps51:innodb_thread_concurrency_timer_based_page>`
      - :ref:`InnoDB timer-based Concurrency Throttling <ps55:innodb_thread_concurrency_timer_based_page>`
      - Replaced by the upstream implementation [#n-5]_
@@ -208,9 +208,6 @@
    * - Feature not implemented
      - Feature not implemented
      - :ref:`Per-query variable statement <ps56:per_query_variable_statement>`
-   * - Feature not implemented
-     - :ref:`Extended mysqlbinlog <ps55:extended_mysqlbinlog>`
-     - :ref:`Extended mysqlbinlog <ps56:extended_mysqlbinlog>`
    
 
 Other Reading

=== modified file 'doc/source/release-notes/Percona-Server-5.6.16-64.0.rst'
--- doc/source/release-notes/Percona-Server-5.6.16-64.0.rst	2014-03-03 18:32:52 +0000
+++ doc/source/release-notes/Percona-Server-5.6.16-64.0.rst	2014-03-10 15:06:07 +0000
@@ -1,47 +1,69 @@
 .. rn:: 5.6.16-64.0
 
-=================================================
- |Percona Server| 5.6.16-64.0 [Not Released Yet]
-=================================================
+==============================
+ |Percona Server| 5.6.16-64.0 
+==============================
 
-Percona is glad to announce the release of |Percona Server| 5.6.16-64.0 on March 6th, 2014 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.16-64.0/>`_ and from the :doc:`Percona Software Repositories </installation>`).
+Percona is glad to announce the release of |Percona Server| 5.6.16-64.0 on March 10th, 2014 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.16-64.0/>`_ and from the :doc:`Percona Software Repositories </installation>`).
 
 Based on `MySQL 5.6.16 <http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-16.html>`_, including all the bug fixes in it, |Percona Server| 5.6.16-64.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.16-64.0 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.6.16-64.0>`_.
 
 New Features
 ============
 
- |Percona Server| now supports :ref:`tokudb_compression` algorithms.
-
- In order to comply with Linux distribution packaging standards |Percona|'s version of ``libmysqlclient`` has been renamed to ``libperconaserver``. The reason this was done was to avoid name conflicts with packages upstream name and library conflicts, otherwise, ``libmysqlclient`` and ``libperconaserverclient`` of same version have no differences. Users will have to use ``libmysqlclient`` of respective distributions, for *CentOS* it is ``mysql-libs`` and for *Ubuntu*/*Debian* it is ``libmysqlclient18`` package. 
- 
+ |Percona Server| has implemented :ref:`backup_locks` that can be used as a lightweight alternative to ``FLUSH TABLES WITH READ LOCK`` for taking physical and logical backups.
+
+ |Percona Server| has split a new :ref:`lru_manager_thread` out of the InnoDB cleaner thread, that performs ``LRU`` flushes and evictions to refill the free lists.
+
+ |Percona Server| now has server-side support for :ref:`tokudb_compression` option syntax.
+
+ |Percona Server| has implemented :ref:`slowlog_rotation` feature to provide users with better control of slow query log disk space usage.
+
  :ref:`mysqlbinlog_change_db` has been ported from |Percona Server| 5.1.
 
+ In order to comply with Linux distribution packaging standards |Percona|'s version of ``libmysqlclient`` has been renamed to ``libperconaserver``. The old name was conflicting with the upstream ``libmysqlclient``. Except for packaging, ``libmysqlclient`` and ``libperconaserverclient`` of the same version do not have any differences. Users wishing to continue using ``libmysqlclient`` will have to install the corresponding package of their distribution, such as ``mysql-lib`` for *CentOS* and ``libmysqlclient18`` for *Ubuntu*/*Debian*. Users wishing to build software against ``libperconaserverclient`` should install ``libperconaserverclient-dev`` package. An old version of  Percona-built ``libmysqlclient`` will be available for `download <http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.15-rel63.0/deb/>`_.
+ 
 Bugs Fixed
 ==========
 
+ The |XtraDB| version number in ``univ.i`` was incorrect. Bug fixed :bug:`1277383`.
+ 
+ :ref:`udf_percona_toolkit` were only shipped with RPM packages. Bug fixed :bug:`1159625`.
+
+ A debug server build will crash if, while performing a bulk insert to a partitioned table, one of the partitions will return a failure for ``end_bulk_insert`` handler call. Bug fixed :bug:`1204871` (upstream :mysqlbug:`71270`).
+
  |Percona Server| 5.6 installation on *Debian* would fail due to default config reference to ``/etc/mysql/conf.d`` which didn't exist. Bug fixed :bug:`1206648`.
 
  Due to a regression in the buffer pool mutex split, a combination of |InnoDB| compression, write workload, and multiple active purge threads could lead to a server crash. Bug fixed :bug:`1247021`.
 
- Several fixes for multiple XA engine support in the server have been ported from |MariaDB|. Bugs fixed :bug:`1255551` (upstream :mysqlbug:`70854`) and :bug:`1255549` (upstream :mysqlbug:`47134`).
+ Server would crash on startup when XA support functions were activated by a second storage engine. Fix for this bug was ported from |MariaDB|. Bug fixed :bug:`1255549` (upstream :mysqlbug:`47134`). 
+
+ ``FLUSH STATUS`` could cause a server crash on the next transaction commit if two XA-supporting storage engines are in use. Fix for this bug was ported from |MariaDB|. Bugs fixed :bug:`1255551` (upstream :mysqlbug:`70854`).
  
  ``auth_pam.so`` shared library needed for :ref:`pam_plugin` was missing from ``RPM`` packages. Bug fixed :bug:`1268246`.
 
  Fix for bug :bug:`1227581`, a buffer pool mutex split regression, was not complete, thus a combination of write workload to |InnoDB| compressed table and a tablespace drop could crash the server. Bug fixed :bug:`1269352`.
 
+ Binary RPM packages couldn't be built from source tarballs on *Fedora* 19. Bug fixed :bug:`1229598`.
+
  |Percona Server| compilation with Performance Schema turned off would fail due to regression introduced by the 5.6 priority mutex framework. Bug fixed :bug:`1272747`.
 
- The |InnoDB| page cleaner thread could have incorrectly decided whether the server is busy or idle on some of its iterations and consequently issue a too big flush list flushing request on a busy server, causing performance instabilities. Bug fixed :bug:`1238039`.
+ The |InnoDB| page cleaner thread could have incorrectly decided whether the server is busy or idle on some of its iterations and consequently issue a too big flush list flushing request on a busy server, causing performance instabilities. Bug fixed :bug:`1238039` (upstream :mysqlbug:`71988`).
 
  |Percona Server| had different server version value when installing from Source and from Binary/RPM. Bug fixed :bug:`1244178`.
  
  |InnoDB| did not handle the cases of asynchronous and synchronous I/O requests completing partially or being interrupted. Bugs fixed :bug:`1262500` (upstream :mysqlbug:`54430`), and :bug:`1263087` (*Andrew Gaul*).
 
- Fixed the upstream bug :mysqlbug:`70768`: the fix for upstream bug :mysqlbug:`70768` may cause a high rate of RW lock creations and desctructions, resulting in a performance regression on some workloads. Bug fixed :bug:`1279671`.
+ The fix for upstream bug :mysqlbug:`70768` may cause a high rate of RW lock creations and destructions, resulting in a performance regression on some workloads. Bug fixed :bug:`1279671` (upstream :mysqlbug:`71708`).
 
  *Debian* and *Ubuntu* packaging has been reworked to meet the packaging standards. Bug fixed :bug:`1281261`.
 
  Fixed the ``CMake`` warnings that were happening when ``Makefile`` was generated. Bugs fixed :bug:`1274827`, upstream bug fixed :mysqlbug:`71089` and :bug:`1274411` (upstream :mysqlbug:`71094`).
 
-Other bugs fixed: :bug:`1052636`, :bug:`1014477`, :bug:`1276445`, :bug:`1274827` (upstream :mysqlbug:`71089`), :bug:`1264952`, :bug:`1005787`, :bug:`1285064`, :bug:`1229598`, :bug:`1277505` (upstream :mysqlbug:`71624`), and :bug:`1204871` (upstream :mysqlbug:`71270`).
+ On *Ubuntu* Precise multiple architecture versions of ``libmysqlclient18`` couldn't be installed side by side. Bug fixed :bug:`1052636`.
+
+ |Percona Server| source tree has been reorganized to match the |MySQL| source tree layout closer. Bug fixed :bug:`1014477`.
+
+ Performance schema autosizing heuristics have been updated to account for Percona Server-specific ``wait/synch/mutex/sql/THD::LOCK_temporary_tables`` mutex. Bug fixed :bug:`1264952`.
+
+Other bugs fixed: :bug:`1276445`, :bug:`1005787`, :bug:`1285064`, :bug:`1229598`, and :bug:`1277505` (upstream :mysqlbug:`71624`).

=== modified file 'doc/source/release-notes/release-notes_index.rst'
--- doc/source/release-notes/release-notes_index.rst	2014-03-04 06:02:56 +0000
+++ doc/source/release-notes/release-notes_index.rst	2014-03-10 15:06:07 +0000
@@ -6,8 +6,8 @@
    :maxdepth: 1
    :glob:
 
+   Percona-Server-5.6.16-64.0
    Percona-Server-5.6.16-64.0-tokudb
-   Percona-Server-5.6.16-64.0
    Percona-Server-5.6.15-63.0
    Percona-Server-5.6.14-62.0
    Percona-Server-5.6.13-61.0

=== modified file 'doc/source/upstream-bug-fixes.rst'
--- doc/source/upstream-bug-fixes.rst	2014-03-03 17:51:33 +0000
+++ doc/source/upstream-bug-fixes.rst	2014-03-10 15:06:07 +0000
@@ -5,9 +5,63 @@
 =============================================================
 
 +-------------------------------------------------------------------------------------------------------------+
+|:Upstream bug: :mysqlbug:`71988` - page_cleaner: aggressive background flushing                              |
+|:Launchpad bug: :bug:`1238039`                                                                               |
+|:Upstream state: Verified (checked on 2014-03-10)                                                            |
+|:Fix Released: :rn:`5.6.16-64.0`                                                                             |
+|:Upstream fix: N/A                                                                                           |
++-------------------------------------------------------------------------------------------------------------+
+|:Upstream bug: :mysqlbug:`71624` - printf size_t results in a fatal warning in 32-bit debug builds           |
+|:Launchpad bug: :bug:`1277505`                                                                               |
+|:Upstream state: Can't repeat (checked on 2014-03-07)                                                        |
+|:Fix Released: :rn:`5.6.16-64.0`                                                                             |
+|:Upstream fix: N/A                                                                                           |
++-------------------------------------------------------------------------------------------------------------+
+|:Upstream bug: :mysqlbug:`71094` - ssl.cmake related warnings                                                |
+|:Launchpad bug: :bug:`1274411`                                                                               |
+|:Upstream state: Closed                                                                                      |
+|:Fix Released: :rn:`5.6.16-64.0`                                                                             |
+|:Upstream fix: N/A                                                                                           |
++-------------------------------------------------------------------------------------------------------------+
+|:Upstream bug: :mysqlbug:`71089` - CMake warning when generating Makefile                                    |
+|:Launchpad bug: :bug:`1274827`                                                                               |
+|:Upstream state: Closed                                                                                      |
+|:Fix Released: :rn:`5.6.16-64.0`                                                                             |
+|:Upstream fix: 5.6.18                                                                                        |
++-------------------------------------------------------------------------------------------------------------+
+|:Upstream bug: :mysqlbug:`71708` - 70768 fix perf regression: high rate of RW lock creation and destruction  |
+|:Launchpad bug: :bug:`1279671`                                                                               |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
+|:Fix Released: :rn:`5.6.16-64.0`                                                                             |
+|:Upstream fix: N/A                                                                                           |
++-------------------------------------------------------------------------------------------------------------+
+|:Upstream bug: :mysqlbug:`54430` - innodb should retry partial reads/writes where errno was 0                |
+|:Launchpad bug: :bug:`1262500`                                                                               |
+|:Upstream state: Closed                                                                                      |
+|:Fix Released: :rn:`5.6.16-64.0`                                                                             |
+|:Upstream fix: N/A                                                                                           |
++-------------------------------------------------------------------------------------------------------------+
+|:Upstream bug: :mysqlbug:`70854` - Tc_log_page_size should be unflushable or server crashes if 2 XA SEs ...  |
+|:Launchpad bug: :bug:`1255551`                                                                               |
+|:Upstream state: Closed                                                                                      |
+|:Fix Released: :rn:`5.6.16-64.0`                                                                             |
+|:Upstream fix: N/A                                                                                           |
++-------------------------------------------------------------------------------------------------------------+
+|:Upstream bug: :mysqlbug:`47134` - Crash on startup when XA support functions activated by a second engine   |
+|:Launchpad bug: :bug:`1255549`                                                                               |
+|:Upstream state: Closed                                                                                      |
+|:Fix Released: :rn:`5.6.16-64.0`                                                                             |
+|:Upstream fix: N/A                                                                                           |
++-------------------------------------------------------------------------------------------------------------+
+|:Upstream bug: :mysqlbug:`71270` - Failures to end bulk insert for partitioned tables handled incorrectly    |
+|:Launchpad bug: :bug:`1204871`                                                                               |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
+|:Fix Released: :rn:`5.6.16-64.0`                                                                             |
+|:Upstream fix: N/A                                                                                           |
++-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`71217` - Threadpool - add thd_wait_begin/thd_wait_end to the network IO functions  |
 |:Launchpad bug: :bug:`1159743`                                                                               |
-|:Upstream state: Open (checked on 2014-02-05)                                                                |
+|:Upstream state: Open (checked on 2014-03-07)                                                                |
 |:Fix Released: :rn:`5.6.15-63.0`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -25,7 +79,7 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`71411` - buf_flush_LRU() does not return correct number in case of compressed pages|
 |:Launchpad bug: :bug:`1231918`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.13-61.0`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -37,7 +91,7 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`70490` - Suppression is too strict on some systems                                 |
 |:Launchpad bug: :bug:`1205196`                                                                               |
-|:Upstream state: No Feedback (checked on 2014-02-05)                                                         |
+|:Upstream state: No Feedback (checked on 2014-03-07)                                                         |
 |:Fix Released: :rn:`5.6.13-61.0`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -49,7 +103,7 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`70500` - Page cleaner should perform LRU flushing regardless of server activity    |
 |:Launchpad bug: :bug:`1234562`                                                                               |
-|:Upstream state: Open (checked on 2014-02-05)                                                                |
+|:Upstream state: Open (checked on 2014-03-07)                                                                |
 |:Fix Released: :rn:`5.6.13-61.0`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -67,31 +121,31 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`68481` - InnoDB LRU flushing for MySQL 5.6 needs work                              |
 |:Launchpad bug: :bug:`1232406`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.13-61.0`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`70453` - Add hard timeouts to page cleaner flushes                                 |
 |:Launchpad bug: :bug:`1232101`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.13-61.0`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`69170` - buf_flush_LRU is lazy                                                     |
 |:Launchpad bug: :bug:`1231918`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.13-61.0`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`68555` - thread convoys from log_checkpoint_margin with innodb_buffer_pool_inst... |
 |:Launchpad bug: :bug:`1236884`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.13-61.0`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`70228` - Is buf_LRU_free_page() really supposed to make non-zip block sticky at ...|
 |:Launchpad bug: :bug:`1220544`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.13-60.6`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -109,13 +163,13 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`70216` - Unnecessary overhead from persistent adaptive hash index latches          |
 |:Launchpad bug: :bug:`1218347`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.13-60.6`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`62018` - innodb adaptive hash index mutex contention                               |
 |:Launchpad bug: :bug:`1216804`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.13-60.6`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -133,13 +187,13 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`42415` - UPDATE/DELETE with LIMIT clause unsafe for SBL even with ORDER BY PK ...  |
 |:Launchpad bug: :bug:`1132194`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.13-60.5`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`69639` - mysql failed to build with dtrace Sun D 1.11                              |
 |:Launchpad bug: :bug:`1196460`                                                                               |
-|:Upstream state: Open (checked on 2014-02-05)                                                                |
+|:Upstream state: Open (checked on 2014-03-07)                                                                |
 |:Fix Released: :rn:`5.6.13-60.5`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -157,13 +211,19 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`69856` - mysql_install_db does not function properly in 5.6 for debug builds       |
 |:Launchpad bug: :bug:`1179359`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.12-60.4`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
+|:Upstream bug: :mysqlbug:`71603` - file name is not escaped in binlog for LOAD DATA INFILE statement         |
+|:Launchpad bug: :bug:`1277351`                                                                               |
+|:Upstream state: N/A                                                                                         |
+|:Fix Released: :rn:`5.6.11-60.3`                                                                             |
+|:Upstream fix: N/A                                                                                           |
++-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`71183` - os_file_fsync() should handle fsync() returning EINTR                     |
 |:Launchpad bug: :bug:`1262651`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -181,7 +241,7 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`69252` - All the parts.partition_max* tests are broken with MTR --parallel         |
 |:Launchpad bug: :bug:`1180481`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -193,7 +253,7 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`68714` - Remove literal statement digest values from perfschema tests              |
 |:Launchpad bug: :bug:`1157078`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -217,13 +277,13 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`68970` - fsp_reserve_free_extents switches from small to big tblspace handling ... |
 |:Launchpad bug: :bug:`1169494`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`68713` - create_duplicate_weedout_tmp_table() leaves key_part_flag uninitialized   |
 |:Launchpad bug: :bug:`1157037`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -235,13 +295,13 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`68999` - SSL_OP_NO_COMPRESSION not defined                                         |
 |:Launchpad bug: :bug:`1183610`                                                                               |
-|:Upstream state: No Feedback (checked on 2014-02-05)                                                         |
+|:Upstream state: No Feedback (checked on 2014-03-07)                                                         |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`68845` - Unnecessary log_sys->mutex reacquisition in mtr_log_reserve_and_write()   |
 |:Launchpad bug: :bug:`1163439`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -271,7 +331,7 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`68476` - Suboptimal code in my_strnxfrm_simple()                                   |
 |:Launchpad bug: :bug:`1132350`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -325,13 +385,13 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`61180` - korr/store macros in my_global.h assume the argument to be a char pointer |
 |:Launchpad bug: :bug:`1042517`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Closed                                                                                      |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|
 |:Launchpad bug: :bug:`1042517`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -343,7 +403,7 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no.  | 
 |:Launchpad bug: :bug:`1013432`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -373,13 +433,13 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`25007` - memory tables with dynamic rows format                                    |
 |:Launchpad bug: N/A                                                                                          |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect    |
 |:Launchpad bug: :bug:`800035`                                                                                |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.11-60.3`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -391,7 +451,7 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`68116` - InnoDB monitor may hit an assertion error in buf_page_get_gen in debug ...|
 |:Launchpad bug: :bug:`1100178`                                                                               |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.10-60.2`                                                                             |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
@@ -403,13 +463,13 @@
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`20001` - Support for temp-tables in INFORMATION_SCHEMA                             |
 |:Launchpad bug: N/A                                                                                          |
-|:Upstream state: Verified (checked on 2014-02-05)                                                            |
+|:Upstream state: Verified (checked on 2014-03-07)                                                            |
 |:Fix Released: :rn:`5.6.5-60.0`                                                                              |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+
 |:Upstream bug: :mysqlbug:`69146` - Optimization in buf_pool_get_oldest_modification if srv_buf_pool_instances|
 |:Launchpad bug: :bug:`1176496`                                                                               |
-|:Upstream state: Open (checked on 2014-02-05)                                                                |
+|:Upstream state: Open (checked on 2014-03-07)                                                                |
 |:Fix Released: :rn:`5.6.5-60.0`                                                                              |
 |:Upstream fix: N/A                                                                                           |
 +-------------------------------------------------------------------------------------------------------------+