Merge lp:~hrvojem/percona-server/bug1187324-5.6 into lp:percona-server/5.6

Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Laurynas Biveinis
Approved revision: 387
Merged at revision: 387
Proposed branch: lp:~hrvojem/percona-server/bug1187324-5.6
Merge into: lp:percona-server/5.6
Diff against target: 69 lines (+11/-27)
2 files modified
doc/source/diagnostics/process_list.rst (+11/-6)
doc/source/performance/query_cache_enhance.rst (+0/-21)
To merge this branch: bzr merge lp:~hrvojem/percona-server/bug1187324-5.6
Reviewer Review Type Date Requested Status
Laurynas Biveinis (community) Approve
Review via email: mp+170366@code.launchpad.net
To post a comment you must log in.
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/diagnostics/process_list.rst'
2--- doc/source/diagnostics/process_list.rst 2013-05-27 13:59:13 +0000
3+++ doc/source/diagnostics/process_list.rst 2013-06-19 13:58:30 +0000
4@@ -19,6 +19,9 @@
5
6 * Added column ``TIME_MS`` to table ``PROCESSLIST``.
7
8+ * :rn:`5.6.11-60.3`:
9+
10+ * Added ``ROWS_SENT`` and ``ROWS_EXAMINED`` columns to table ``PROCESSLIST``.`
11
12 INFORMATION_SCHEMA Tables
13 =========================
14@@ -36,6 +39,8 @@
15 :column STATE: An action, event, or state that indicates what the thread is doing.
16 :column INFO: The statement that the thread is executing, or NULL if it is not executing any statement.
17 :column TIME_MS: The time in milliseconds that the thread has been in its current state.
18+ :column ROWS_SENT: The number of rows query sent.
19+ :column ROWS_EXAMINED: The number of rows scanned for a query.
20
21
22 Example Output
23@@ -45,9 +50,9 @@
24
25 mysql> SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST;
26
27- +----+------+-----------+--------------------+---------+------+-----------+----------------------------------------------+---------+
28- | ID | USER | HOST | DB | COMMAND | TIME | STATE | INFO | TIME_MS |
29- +----+------+-----------+--------------------+---------+------+-----------+----------------------------------------------+---------+
30- | 5 | root | localhost | information_schema | Query | 0 | executing | select * from information_schema.PROCESSLIST | 0 |
31- +----+------+-----------+--------------------+---------+------+-----------+----------------------------------------------+---------+
32-
33+ +----+------+-----------+--------------------+---------+------+-----------+---------------------------+---------+-----------+---------------+
34+ | ID | USER | HOST | DB | COMMAND | TIME | STATE | INFO | TIME_MS | ROWS_SENT | ROWS_EXAMINED |
35+ +----+------+-----------+--------------------+---------+------+-----------+---------------------------+---------+-----------+---------------+
36+ | 12 | root | localhost | information_schema | Query | 0 | executing | select * from processlist | 0 | 0 | 0 |
37+ +----+------+-----------+--------------------+---------+------+-----------+---------------------------+---------+-----------+---------------+
38+
39
40=== modified file 'doc/source/performance/query_cache_enhance.rst'
41--- doc/source/performance/query_cache_enhance.rst 2013-06-03 10:01:08 +0000
42+++ doc/source/performance/query_cache_enhance.rst 2013-06-19 13:58:30 +0000
43@@ -12,27 +12,6 @@
44
45 * Ignoring comments
46
47-Disabling the cache completely
48-==============================
49-
50-This feature allows the user to completely disable use of the query cache. When the server is compiled with the query cache enabled, the query cache is locked during use by the query cache mutex. This lock can cause performance to decrease in some situations. By disabling use of the query cache altogether when the server is started, any possibility of locking it is eliminated, and performance may be improved.
51-
52-The query cache can now be disabled at server startup or in an option file by: ::
53-
54- --query_cache_type=0
55-
56-The default is 1 (query cache enabled).
57-
58-**Note:** This variable already exists in standard |MySQL|, but when setting query_cache_type=0, the query cache mutex will still be in used. Setting query_cache_type=0 in |Percona Server| ensures that both the cache is disabled and the mutex is not used.
59-
60-If query caching is off and a user tries to turn it on from within a session, the following error will be reported: ::
61-
62- SET GLOBAL query_cache_type=ON;
63- ERROR 1651(HY000): Query cache is disabled; restart the server with query_cache_type=1 to enable it
64-
65-**Note:** This variable is implemented in standard |MySQL| from version 5.5.0.
66-
67-
68 Diagnosing contention more easily
69 =================================
70

Subscribers

People subscribed via source and target branches