Merge lp:~hrvojem/percona-server/bug868002-5.5 into lp:percona-server/5.5

[Hrvoje Matijakovic]

[Laurynas Biveinis (laurynas-biveinis)]

review: Approve

[Alexey Kopytov (akopytov)]

Couple of comments:

1. The log_slow_filter value accepted by the server is qc_miss rather than qc_hit. Which is inconsistent with the "QC_Hit:" value printed in the slow log, but we have to live with that as we cannot change it in stable releases. However, the documentation for log_slow_filter is now incorrect.

2. The bug (more precisely, item(2) from the report) applies to both 5.1 and 5.5. I'm going to target it to 5.1 series.

review: Needs Fixing

=== modified file 'doc/source/diagnostics/slow_extended_55.rst'
--- doc/source/diagnostics/slow_extended_55.rst	2012-08-03 08:58:37 +0000
+++ doc/source/diagnostics/slow_extended_55.rst	2012-09-05 13:11:20 +0000
@@ -42,8 +42,8 @@
 
 Filters the slow log by the query's execution plan. The value is a comma-delimited string, and can contain any combination of the following values:
 
-  * ``qc_miss``:
-    The query was not found in the query cache.
+  * ``qc_hit``:
+    The query was found in the query cache.
 
   * ``full_scan``:
     The query performed a full table scan.
@@ -259,20 +259,43 @@
 
   # User@Host: mailboxer[mailboxer] @  [192.168.10.165]
   # Thread_id: 11167745  Schema: board
-  # QC_Hit: No  Full_scan: No  Full_join: No  Tmp_table: Yes  Disk_tmp_table: No
-  # Filesort: Yes  Disk_filesort: No  Merge_passes: 0
-  # Query_time: 0.000659  Lock_time: 0.000070  Rows_sent: 0  Rows_examined: 30  Rows_affected: 0  Rows_read: 30
-  #   innodb_IO_r_ops: 1  innodb_IO_r_bytes: 16384  innodb_IO_r_wait: 0.028487
-  #   innodb_rec_lock_wait: 0.000000  innodb_queue_wait: 0.000000
-  #   innodb_pages_distinct: 5
-  select count(distinct author_id) from art87.article87 force index (forum_id) where forum_id = 240215 and thread_id = ``710575`` 
+  # Query_time: 1.009400  Lock_time: 0.000190  Rows_sent: 4  Rows_examined: 1543719  Rows_affected: 0  Rows_read: 4
+  # Bytes_sent: 278  Tmp_tables: 0  Tmp_disk_tables: 0  Tmp_table_sizes: 0
+  # InnoDB_trx_id: 1500
+  # QC_Hit: No  Full_scan: Yes  Full_join: No  Tmp_table: No  Tmp_table_on_disk: No
+  # Filesort: No  Filesort_on_disk: No  Merge_passes: 0
+  #   InnoDB_IO_r_ops: 6415  InnoDB_IO_r_bytes: 105103360  InnoDB_IO_r_wait: 0.001279
+  #   InnoDB_rec_lock_wait: 0.000000  InnoDB_queue_wait: 0.000000
+  #   InnoDB_pages_distinct: 6430
+  SET timestamp=1346844943;
+  SELECT id,title,production_year FROM title WHERE title = 'Bambi';
 
 Another example (:variable:`log_slow_verbosity` ``=profiling``): ::
 
-  # Query_time: 4.555235  Lock_time: 0.000000  Rows_sent: 1  Rows_examined: 0  Rows_affected: 0  Rows_read: 1
-  # Profile_starting: 4.554799 Profile_starting_cpu: 0.000000 Profile_checking_permissions: 0.000095 Profile_checking_permissions_cpu: 0.000000 Profile_Opening_tables: 0.000088 Profile_Opening_tables_cpu: 0.000000 Profile_init: 0.000056 Profile_init_cpu: 0.000000 Profile_optimizing: 0.000046 Profile_optimizing_cpu: 0.000000 Profile_executing: 0.000098 Profile_executing_cpu: 0.000000 Profile_end: 0.000049 Profile_end_cpu: 0.000000 Profile_query_end: 0.000045 Profile_query_end_cpu: 0.000000 Profile_freeing_items: 0.000084 Profile_freeing_items_cpu: 0.000000 Profile_logging_slow_query: 0.000045 Profile_logging_slow_query_cpu: 0.000000 
-  # Profile_total: 4.555405 Profile_total_cpu: 0.000000 
-  insert into teee4 select * from teee4 limit 10000000;
+  # Query_time: 0.962742  Lock_time: 0.000202  Rows_sent: 4  Rows_examined: 1543719  Rows_affected: 0  Rows_read: 4
+  # Bytes_sent: 278  Tmp_tables: 0  Tmp_disk_tables: 0  Tmp_table_sizes: 0
+  # Profile_starting: 0.000030 Profile_starting_cpu: 0.000028 Profile_Waiting_for_query_cache_lock: 0.000003 
+    Profile_Waiting_for_query_cache_lock_cpu: 0.000003 Profile_Waiting_on_query_cache_mutex: 0.000003 
+    Profile_Waiting_on_query_cache_mutex_cpu: 0.000003 Profile_checking_query_cache_for_query: 0.000076 
+    Profile_checking_query_cache_for_query_cpu: 0.000076 Profile_checking_permissions: 0.000011 
+    Profile_checking_permissions_cpu: 0.000011 Profile_Opening_tables: 0.000078 Profile_Opening_tables_cpu: 0.000078 
+    Profile_System_lock: 0.000022 Profile_System_lock_cpu: 0.000022 Profile_Waiting_for_query_cache_lock: 0.000003 
+    Profile_Waiting_for_query_cache_lock_cpu: 0.000002 Profile_Waiting_on_query_cache_mutex: 0.000054 
+    Profile_Waiting_on_query_cache_mutex_cpu: 0.000054 Profile_init: 0.000039 Profile_init_cpu: 0.000040 
+    Profile_optimizing: 0.000015 Profile_optimizing_cpu: 0.000014 Profile_statistics: 0.000021 Profile_statistics_cpu: 0.000021 
+    Profile_preparing: 0.000020 Profile_preparing_cpu: 0.000020 Profile_executing: 0.000003 Profile_executing_cpu: 0.000003 
+    Profile_Sending_data: 0.962324 Profile_Sending_data_cpu: 0.961526 Profile_end: 0.000006 Profile_end_cpu: 0.000005 
+    Profile_query_end: 0.000004 Profile_query_end_cpu: 0.000004 Profile_closing_tables: 0.000008 Profile_closing_tables_cpu: 0.000008 
+    Profile_freeing_items: 0.000007 Profile_freeing_items_cpu: 0.000007 Profile_Waiting_for_query_cache_lock: 0.000000 
+    Profile_Waiting_for_query_cache_lock_cpu: 0.000001 Profile_Waiting_on_query_cache_mutex: 0.000001 
+    Profile_Waiting_on_query_cache_mutex_cpu: 0.000001 Profile_freeing_items: 0.000017 Profile_freeing_items_cpu: 0.000016 
+    Profile_Waiting_for_query_cache_lock: 0.000001 Profile_Waiting_for_query_cache_lock_cpu: 0.000001 
+    Profile_Waiting_on_query_cache_mutex: 0.000000 Profile_Waiting_on_query_cache_mutex_cpu: 0.000001 
+    Profile_freeing_items: 0.000001 Profile_freeing_items_cpu: 0.000001 Profile_storing_result_in_query_cache: 0.000002 
+    Profile_storing_result_in_query_cache_cpu: 0.000002 Profile_logging_slow_query: 0.000001 Profile_logging_slow_query_cpu: 0.000001 
+  # Profile_total: 0.962751 Profile_total_cpu: 0.961950 
+  # InnoDB_trx_id: 1700
+  
 
 Connection and Schema Identifier
 --------------------------------
@@ -290,7 +313,7 @@
 
 The feature also adds information about how many rows were examined for ``SELECT`` queries, and how many were analyzed and affected for ``UPDATE``, ``DELETE``, and ``INSERT`` queries, ::
 
-  # Query_time: 0.000659  Lock_time: 0.000070  Rows_sent: 0  Rows_examined: 30  Rows_affected: 0  Rows_read: 30
+  # Query_time: 0.962742  Lock_time: 0.000202  Rows_sent: 4  Rows_examined: 1543719  Rows_affected: 0  Rows_read: 4
 
 Values and context:
 
@@ -306,7 +329,7 @@
 Memory Footprint
 ----------------
 
-The feature provides information about the amount of bytes sent for the result of the query and the number of temporary tables created for its execution - differentiated by whether they were created on memory or on disk - with the total number of bytes used by them. ::
+The feature provides information about the amount of bytes sent for the result of the query and the number of temporary tables created for its execution - differentiated by whether they were created on memory or on disk - with the total number of bytes used by them. :: 
 
   # Bytes_sent: 8053  Tmp_tables: 1  Tmp_disk_tables: 0  Tmp_table_sizes: 950528
 
@@ -330,8 +353,8 @@
 
 Each query can be executed in various ways. For example, it may use indexes or do a full table scan, or a temporary table may be needed. These are the things that you can usually see by running ``EXPLAIN`` on the query. The feature will now allow you to see the most important facts about the execution in the log file. ::
 
-  # QC_Hit: No  Full_scan: No  Full_join: No  Tmp_table: Yes  Disk_tmp_table: No
-  # Filesort: Yes  Disk_filesort: No  Merge_passes: 0
+  # QC_Hit: No  Full_scan: Yes  Full_join: No  Tmp_table: No  Tmp_table_on_disk: No
+  # Filesort: No  Filesort_on_disk: No  Merge_passes: 0
 
 The values and their meanings are documented with the :variable:`log_slow_filter` option.
 
@@ -340,9 +363,9 @@
 
 The final part of the output is the |InnoDB| usage statistics. |MySQL| currently shows many per-session statistics for operations with ``SHOW SESSION STATUS``, but that does not include those of |InnoDB|, which are always global and shared by all threads. This feature lets you see those values for a given query. ::
 
-  # innodb_IO_r_ops: 1  innodb_IO_r_bytes: 16384  innodb_IO_r_wait: 0.028487
-  # innodb_rec_lock_wait: 0.000000  innodb_queue_wait: 0.000000
-  # innodb_pages_distinct: 5
+  #   InnoDB_IO_r_ops: 6415  InnoDB_IO_r_bytes: 105103360  InnoDB_IO_r_wait: 0.001279
+  #   InnoDB_rec_lock_wait: 0.000000  InnoDB_queue_wait: 0.000000
+  #   InnoDB_pages_distinct: 6430
 
 Values:
 
 
=== modified file 'doc/source/installation/apt_repo.rst'
--- doc/source/installation/apt_repo.rst	2012-06-04 13:39:55 +0000
+++ doc/source/installation/apt_repo.rst	2012-09-05 13:11:20 +0000
@@ -49,14 +49,13 @@
  * 12.04LTS (precise)
 
 
-Release Candidate Repository
-============================
-
-To subscribe to the release candidate repository, add two lines to the :file:`/etc/apt/sources.list` file, again replacing ``VERSION`` with your server's release version: ::
-
-  deb http://repo.percona.com/apt-rc VERSION main
-  deb-src http://repo.percona.com/apt-rc VERSION main
-
+Percona `apt` Experimental repository
+=====================================
+
+Percona offers fresh beta builds from the experimental repository. To enable it add the following lines to your  :file:`/etc/apt/sources.list` , replacing ``VERSION`` with the name of your distribution: ::
+
+  deb http://repo.percona.com/apt VERSION main experimental
+  deb-src http://repo.percona.com/apt VERSION main experimental
 
 Apt-Pinning the packages
 ========================
 
=== modified file 'doc/source/installation/yum_repo.rst'
--- doc/source/installation/yum_repo.rst	2012-01-09 04:35:32 +0000
+++ doc/source/installation/yum_repo.rst	2012-09-05 13:11:20 +0000
@@ -73,9 +73,12 @@
 
 * *Amazon Linux AMI* (works the same as *CentOS* 5)
 
-Release Candidate Repository
-============================
-
-To subscribe to the release candidate repository, install the release candidate (RC) *RPM*: ::
-
-  rpm -Uhv http://www.percona.com/downloads/percona-release/percona-rc-0.0-2.x86_64.rpm
+Percona `yum` Experimental repository
+=====================================
+
+Percona offers fresh beta builds from the experimental repository. To subscribe to the experimental repository, install the experimental *RPM*: ::
+
+  rpm -Uhv http://repo.percona.com/testing/centos/6/os/noarch/percona-testing-0.0-1.noarch.rpm
+
+.. note:: 
+ This repository works for both RHEL/CentOS 5 and RHEL/CentOS 6
 
=== modified file 'doc/source/release-notes/Percona-Server-5.5.27-28.1.rst'
--- doc/source/release-notes/Percona-Server-5.5.27-28.1.rst	2012-09-03 13:31:37 +0000
+++ doc/source/release-notes/Percona-Server-5.5.27-28.1.rst	2012-09-05 13:11:20 +0000
@@ -11,7 +11,7 @@
 Bug Fixes
 =========
 
- |Percona Server| :rn:`5.5.27-28.0` would crash or deadlock in |XtraDB| buffer pool code. This was caused by incorrect mutex handling in recently introduced |InnoDB| code. Bug fixed :bug:`1038225` (*Laurynas Biveinis*).
+ |Percona Server| :rn:`5.5.27-28.0` would crash or deadlock in |XtraDB| buffer pool code. This was caused by incorrect mutex handling in porting of the recently introduced InnoDB code to |XtraDB|. Bug fixed :bug:`1038225` (*Laurynas Biveinis*).
 
  Variables :variable:`innodb_adaptive_flushing_method` and :variable:`innodb_flush_neighbor_pages` would not correctly translate some values internally. Bug fixed :bug:`1039384` (*Laurynas Biveinis*).