Merge lp:~laurynas-biveinis/percona-server/5.6-merge-1-fixes into lp:percona-server/5.6

Proposed by Laurynas Biveinis on 2013-05-21
Status: Merged
Approved by: Alexey Kopytov on 2013-05-22
Approved revision: no longer in the source branch.
Merged at revision: 350
Proposed branch: lp:~laurynas-biveinis/percona-server/5.6-merge-1-fixes
Merge into: lp:percona-server/5.6
Prerequisite: lp:~laurynas-biveinis/percona-server/5.6-merge-1
Diff against target: 2267 lines (+1581/-452)
32 files modified
.bzrignore (+0/-1)
Percona-Server/client/CMakeLists.txt (+0/-1)
Percona-Server/mysql-test/r/disabled_replication.result (+1/-2)
Percona-Server/mysql-test/suite/sys_vars/r/innodb_page_size_basic.result (+3/-0)
Percona-Server/sql/mysqld.h (+1/-1)
Percona-Server/sql/sql_connect.cc (+1/-1)
Percona-Server/sql/sql_parse.cc (+1/-10)
Percona-Server/sql/sys_vars.h (+0/-9)
Percona-Server/storage/heap/hp_info.c (+1/-1)
Percona-Server/storage/innobase/include/univ.i (+1/-1)
Percona-Server/storage/innobase/sync/sync0rw.cc (+1/-1)
Percona-Server/storage/innobase/sync/sync0sync.cc (+1/-17)
Percona-Server/storage/myisam/mi_check.c (+1/-1)
Percona-Server/storage/myisam/sort.c (+1/-1)
doc/Makefile (+0/-145)
doc/make.bat (+170/-0)
doc/source/diagnostics/innodb_deadlock_count.rst (+57/-0)
doc/source/diagnostics/innodb_show_lock_names.rst (+24/-0)
doc/source/diagnostics/innodb_show_status.rst (+475/-0)
doc/source/diagnostics/misc_info_schema_tables.rst (+48/-0)
doc/source/diagnostics/mysql_syslog.rst (+43/-0)
doc/source/diagnostics/process_list.rst (+53/-0)
doc/source/diagnostics/show_engines.rst (+40/-0)
doc/source/diagnostics/slow_extended_55.rst (+377/-0)
doc/source/diagnostics/thread_based_profiling.rst (+17/-0)
doc/source/diagnostics/user_stats.rst (+242/-0)
doc/source/flexibility/mysqldump_ignore_create_error.rst (+22/-0)
doc/source/reliability/error_pad.rst (+0/-55)
doc/source/reliability/innodb_corrupt_table_action.rst (+0/-35)
doc/source/reliability/log_connection_error.rst (+0/-14)
doc/source/reliability/show_slave_status_nolock.rst (+0/-23)
doc/source/upstream-bug-fixes.rst (+0/-133)
To merge this branch: bzr merge lp:~laurynas-biveinis/percona-server/5.6-merge-1-fixes
Reviewer Review Type Date Requested Status
Alexey Kopytov (community) 2013-05-21 Approve on 2013-05-22
Percona core 2013-05-21 Pending
Review via email: mp+164948@code.launchpad.net

This proposal supersedes a proposal from 2013-05-20.

Description of the change

2nd MP: rebased on the correct branch.
http://jenkins.percona.com/job/percona-server-5.6-param/109/

Post-review fixes for the lp:percona-server/5.5 rev 397 merge to
lp:percona-server/5.6.

- Revert the spurious copyright comment changes, so that they match
  the ones at the current lp:mysql-server/5.6. Do not touch the ones
  that are fixed in the subsequent 5.6.11 merge.

- Revert the change introduced at the porting where SHOW SLAVE STATUS
  would check whether the slave is running, and returning
  WARN_NO_MASTER_INFO warning if it's not. Re-record
  disabled_replication test to match.

- Remove introduced-by-mistake debugging printf()s in sys_vars.h.

- Fix Percona InnoDB version in univ.i.

- Remove obsolete UNIV_SRV_PRINT_LATCH_WAITS code.

To post a comment you must log in.
Laurynas Biveinis (laurynas-biveinis) wrote : Posted in a previous version of this proposal

Local test and long and a hard stare at the diff instead of Jenkins. http://jenkins.percona.com/job/percona-server-5.6-param/107/ could be checked in a week's or so time though.

Alexey Kopytov (akopytov) wrote : Posted in a previous version of this proposal

Jenkins test failures. Will be resubmitted as discussed on IRC.

review: Resubmit

Revisions 350--352 that are to be merged here do not contain sys_vars or doc/ changes. No idea why they appear in the diff.

Alexey Kopytov (akopytov) wrote :

Test failures.

review: Needs Fixing
Alexey Kopytov (akopytov) wrote :

As discussed on IRC, the changed page tests will be fixed after merging to trunk.

review: Approve

Thanks, the bitmap test failures are tracked at https://bugs.launchpad.net/percona-server/+bug/1182793

349. By Laurynas Biveinis on 2013-05-22

Automerge lp:~laurynas-biveinis/percona-server/5.6-merge-1

350. By Laurynas Biveinis on 2013-05-22

Post-review fixes for the lp:percona-server/5.5 rev 397 merge to
lp:percona-server/5.6.

- Revert the spurious copyright comment changes, so that they match
  the ones at the current lp:mysql-server/5.6. Do not touch the ones
  that are fixed in the subsequent 5.6.11 merge.

351. By Laurynas Biveinis on 2013-05-22

Post-review fixes for the lp:percona-server/5.5 rev 397 merge to
lp:percona-server/5.6.

- Revert the change introduced at the porting where SHOW SLAVE STATUS
  would check whether the slave is running, and returning
  WARN_NO_MASTER_INFO warning if it's not. Re-record
  disabled_replication test to match.

352. By Laurynas Biveinis on 2013-05-22

Post-review fixes for the lp:percona-server/5.5 rev 397 merge to
lp:percona-server/5.6.

- Remove introduced-by-mistake debugging printf()s in sys_vars.h.

- Fix Percona InnoDB version in univ.i.

- Remove obsolete UNIV_SRV_PRINT_LATCH_WAITS code.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== removed file '.bzrignore'
--- .bzrignore 2013-05-22 08:54:33 +0000
+++ .bzrignore 1970-01-01 00:00:00 +0000
@@ -1,1 +0,0 @@
1build
20
=== modified file 'Percona-Server/client/CMakeLists.txt'
--- Percona-Server/client/CMakeLists.txt 2013-05-22 08:54:33 +0000
+++ Percona-Server/client/CMakeLists.txt 2013-05-22 08:54:39 +0000
@@ -1,4 +1,3 @@
1# Copyright (c) 2006, 2012, Oracle and/or its affiliates. All rights reserved.
2# Copyright (c) 2006, 2011, Oracle and/or its affiliates. All rights reserved.1# Copyright (c) 2006, 2011, Oracle and/or its affiliates. All rights reserved.
3# 2#
4# This program is free software; you can redistribute it and/or modify3# This program is free software; you can redistribute it and/or modify
54
=== modified file 'Percona-Server/mysql-test/r/disabled_replication.result'
--- Percona-Server/mysql-test/r/disabled_replication.result 2013-05-22 08:54:33 +0000
+++ Percona-Server/mysql-test/r/disabled_replication.result 2012-12-14 15:02:07 +0000
@@ -1,6 +1,5 @@
1SHOW SLAVE STATUS;1SHOW SLAVE STATUS;
2Warnings:2Slave_IO_State Master_Host Master_User Master_Port Connect_Retry Master_Log_File Read_Master_Log_Pos Relay_Log_File Relay_Log_Pos Relay_Master_Log_File Slave_IO_Running Slave_SQL_Running Replicate_Do_DB Replicate_Ignore_DB Replicate_Do_Table Replicate_Ignore_Table Replicate_Wild_Do_Table Replicate_Wild_Ignore_Table Last_Errno Last_Error Skip_Counter Exec_Master_Log_Pos Relay_Log_Space Until_Condition Until_Log_File Until_Log_Pos Master_SSL_Allowed Master_SSL_CA_File Master_SSL_CA_Path Master_SSL_Cert Master_SSL_Cipher Master_SSL_Key Seconds_Behind_Master Master_SSL_Verify_Server_Cert Last_IO_Errno Last_IO_Error Last_SQL_Errno Last_SQL_Error Replicate_Ignore_Server_Ids Master_Server_Id Master_UUID Master_Info_File SQL_Delay SQL_Remaining_Delay Slave_SQL_Running_State Master_Retry_Count Master_Bind Last_IO_Error_Timestamp Last_SQL_Error_Timestamp Master_SSL_Crl Master_SSL_Crlpath Retrieved_Gtid_Set Executed_Gtid_Set Auto_Position
3Warning 1617 The master info structure does not exist
4RESET SLAVE;3RESET SLAVE;
5ERROR HY000: Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log.4ERROR HY000: Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log.
6SHOW RELAYLOG EVENTS;5SHOW RELAYLOG EVENTS;
76
=== added file 'Percona-Server/mysql-test/suite/sys_vars/r/innodb_page_size_basic.result'
--- Percona-Server/mysql-test/suite/sys_vars/r/innodb_page_size_basic.result 1970-01-01 00:00:00 +0000
+++ Percona-Server/mysql-test/suite/sys_vars/r/innodb_page_size_basic.result 2013-05-22 08:54:39 +0000
@@ -0,0 +1,3 @@
1SELECT @@global.innodb_page_size;
2@@global.innodb_page_size
316384
04
=== modified file 'Percona-Server/sql/mysqld.h'
--- Percona-Server/sql/mysqld.h 2013-05-22 08:54:33 +0000
+++ Percona-Server/sql/mysqld.h 2013-05-22 08:54:39 +0000
@@ -1,4 +1,4 @@
1/* Copyright (c) 2006, 2012, Oracle and/or its affiliates. All rights reserved.1/* Copyright (c) 2010, 2012, Oracle and/or its affiliates. All rights reserved.
22
3 This program is free software; you can redistribute it and/or modify3 This program is free software; you can redistribute it and/or modify
4 it under the terms of the GNU General Public License as published by4 it under the terms of the GNU General Public License as published by
55
=== modified file 'Percona-Server/sql/sql_connect.cc'
--- Percona-Server/sql/sql_connect.cc 2013-05-22 08:54:33 +0000
+++ Percona-Server/sql/sql_connect.cc 2013-05-22 08:54:39 +0000
@@ -1,5 +1,5 @@
1/*1/*
2 Copyright (c) 2007, 2012, Oracle and/or its affiliates. All rights reserved.2 Copyright (c) 2007, 2011, Oracle and/or its affiliates. All rights reserved.
33
4 This program is free software; you can redistribute it and/or modify4 This program is free software; you can redistribute it and/or modify
5 it under the terms of the GNU General Public License as published by5 it under the terms of the GNU General Public License as published by
66
=== modified file 'Percona-Server/sql/sql_parse.cc'
--- Percona-Server/sql/sql_parse.cc 2013-05-22 08:54:33 +0000
+++ Percona-Server/sql/sql_parse.cc 2013-05-22 08:54:39 +0000
@@ -2980,16 +2980,7 @@
2980 {2980 {
2981 mysql_mutex_lock(&LOCK_active_mi);2981 mysql_mutex_lock(&LOCK_active_mi);
2982 }2982 }
2983 if (active_mi != NULL)2983 res = show_slave_status(thd, active_mi);
2984 {
2985 res = show_slave_status(thd, active_mi);
2986 }
2987 else
2988 {
2989 push_warning(thd, Sql_condition::WARN_LEVEL_WARN,
2990 WARN_NO_MASTER_INFO, ER(WARN_NO_MASTER_INFO));
2991 my_ok(thd);
2992 }
2993 if(do_lock)2984 if(do_lock)
2994 {2985 {
2995 mysql_mutex_unlock(&LOCK_active_mi);2986 mysql_mutex_unlock(&LOCK_active_mi);
29962987
=== modified file 'Percona-Server/sql/sys_vars.h'
--- Percona-Server/sql/sys_vars.h 2013-05-22 08:54:33 +0000
+++ Percona-Server/sql/sys_vars.h 2013-05-22 08:54:39 +0000
@@ -193,9 +193,6 @@
193 if (SIGNED)193 if (SIGNED)
194 {194 {
195 longlong max_val= *max_var_ptr();195 longlong max_val= *max_var_ptr();
196 fprintf(stderr, "v = %lld, max_val = %lld\n", v, max_val);
197 fprintf(stderr, "save_result = %lld\n",
198 (longlong)(var->save_result.ulonglong_value));
199 if (((longlong)(var->save_result.ulonglong_value)) > max_val)196 if (((longlong)(var->save_result.ulonglong_value)) > max_val)
200 var->save_result.ulonglong_value= max_val;197 var->save_result.ulonglong_value= max_val;
201 /*198 /*
@@ -218,12 +215,6 @@
218 (getopt_constraint_get_min_value(option.name, 0, FALSE));215 (getopt_constraint_get_min_value(option.name, 0, FALSE));
219 vmax= static_cast<const T *>216 vmax= static_cast<const T *>
220 (getopt_constraint_get_max_value(option.name, 0, FALSE));217 (getopt_constraint_get_max_value(option.name, 0, FALSE));
221 if (vmin)
222 fprintf(stderr, "vmin = signed %lld, unsigned %llu\n",
223 (long long)*vmin, (unsigned long long)*vmin);
224 if (vmax)
225 fprintf(stderr, "vmax = signed %lld, unsigned %llu\n",
226 (long long)*vmax, (unsigned long long)*vmax);
227218
228 if (SIGNED)219 if (SIGNED)
229 {220 {
230221
=== modified file 'Percona-Server/storage/heap/hp_info.c'
--- Percona-Server/storage/heap/hp_info.c 2013-05-22 08:54:33 +0000
+++ Percona-Server/storage/heap/hp_info.c 2013-05-22 08:54:39 +0000
@@ -1,4 +1,4 @@
1/* Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.1/* Copyright (C) 2000-2004 MySQL AB
22
3 This program is free software; you can redistribute it and/or modify3 This program is free software; you can redistribute it and/or modify
4 it under the terms of the GNU General Public License as published by4 it under the terms of the GNU General Public License as published by
55
=== modified file 'Percona-Server/storage/innobase/include/univ.i'
--- Percona-Server/storage/innobase/include/univ.i 2013-05-22 08:54:33 +0000
+++ Percona-Server/storage/innobase/include/univ.i 2013-05-22 08:54:39 +0000
@@ -47,7 +47,7 @@
47#define INNODB_VERSION_BUGFIX MYSQL_VERSION_PATCH47#define INNODB_VERSION_BUGFIX MYSQL_VERSION_PATCH
4848
49#ifndef PERCONA_INNODB_VERSION49#ifndef PERCONA_INNODB_VERSION
50#define PERCONA_INNODB_VERSION 29.350#define PERCONA_INNODB_VERSION 60.3
51#endif51#endif
5252
53/* Enable UNIV_LOG_ARCHIVE in XtraDB */53/* Enable UNIV_LOG_ARCHIVE in XtraDB */
5454
=== modified file 'Percona-Server/storage/innobase/sync/sync0rw.cc'
--- Percona-Server/storage/innobase/sync/sync0rw.cc 2013-05-22 08:54:33 +0000
+++ Percona-Server/storage/innobase/sync/sync0rw.cc 2013-05-22 08:54:39 +0000
@@ -1,6 +1,6 @@
1/*****************************************************************************1/*****************************************************************************
22
3Copyright (c) 1995, 2012, Oracle and/or its affiliates. All Rights Reserved.3Copyright (c) 1995, 2011, Oracle and/or its affiliates. All Rights Reserved.
4Copyright (c) 2008, Google Inc.4Copyright (c) 2008, Google Inc.
55
6Portions of this file contain modifications contributed and copyrighted by6Portions of this file contain modifications contributed and copyrighted by
77
=== modified file 'Percona-Server/storage/innobase/sync/sync0sync.cc'
--- Percona-Server/storage/innobase/sync/sync0sync.cc 2013-05-22 08:54:33 +0000
+++ Percona-Server/storage/innobase/sync/sync0sync.cc 2013-05-22 08:54:39 +0000
@@ -1,6 +1,6 @@
1/*****************************************************************************1/*****************************************************************************
22
3Copyright (c) 1995, 2012, Oracle and/or its affiliates. All Rights Reserved.3Copyright (c) 1995, 2011, Oracle and/or its affiliates. All Rights Reserved.
4Copyright (c) 2008, Google Inc.4Copyright (c) 2008, Google Inc.
55
6Portions of this file contain modifications contributed and copyrighted by6Portions of this file contain modifications contributed and copyrighted by
@@ -514,14 +514,6 @@
514 os_thread_yield();514 os_thread_yield();
515 }515 }
516516
517#ifdef UNIV_SRV_PRINT_LATCH_WAITS
518 fprintf(stderr,
519 "Thread " ULINTPF " spin wait mutex at %p"
520 " '%s' rnds " ULINTPF "\n",
521 os_thread_pf(os_thread_get_curr_id()), (void*) mutex,
522 mutex->cmutex_name, i);
523#endif
524
525 mutex_spin_round_count.add(counter_index, i);517 mutex_spin_round_count.add(counter_index, i);
526518
527 if (ib_mutex_test_and_set(mutex) == 0) {519 if (ib_mutex_test_and_set(mutex) == 0) {
@@ -584,14 +576,6 @@
584 after the change in the wait array and the waiters field was made.576 after the change in the wait array and the waiters field was made.
585 Now there is no risk of infinite wait on the event. */577 Now there is no risk of infinite wait on the event. */
586578
587#ifdef UNIV_SRV_PRINT_LATCH_WAITS
588 fprintf(stderr,
589 "Thread " ULINTPF " OS wait mutex at %p '%s' rnds " ULINTPF
590 "\n",
591 os_thread_pf(os_thread_get_curr_id()), (void*) mutex,
592 mutex->cmutex_name, i);
593#endif
594
595 mutex_os_wait_count.add(counter_index, 1);579 mutex_os_wait_count.add(counter_index, 1);
596580
597 mutex->count_os_wait++;581 mutex->count_os_wait++;
598582
=== modified file 'Percona-Server/storage/myisam/mi_check.c'
--- Percona-Server/storage/myisam/mi_check.c 2013-05-22 08:54:33 +0000
+++ Percona-Server/storage/myisam/mi_check.c 2013-03-05 12:46:43 +0000
@@ -1,5 +1,5 @@
1/*1/*
2 Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved.2 Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.
33
4 This program is free software; you can redistribute it and/or modify4 This program is free software; you can redistribute it and/or modify
5 it under the terms of the GNU General Public License as published by5 it under the terms of the GNU General Public License as published by
66
=== modified file 'Percona-Server/storage/myisam/sort.c'
--- Percona-Server/storage/myisam/sort.c 2013-05-22 08:54:33 +0000
+++ Percona-Server/storage/myisam/sort.c 2013-05-22 08:54:39 +0000
@@ -1,4 +1,4 @@
1/* Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved.1/* Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.
22
3 This program is free software; you can redistribute it and/or modify3 This program is free software; you can redistribute it and/or modify
4 it under the terms of the GNU General Public License as published by4 it under the terms of the GNU General Public License as published by
55
=== removed file 'doc/Makefile'
--- doc/Makefile 2013-05-22 08:54:33 +0000
+++ doc/Makefile 1970-01-01 00:00:00 +0000
@@ -1,145 +0,0 @@
1# Makefile for Sphinx documentation
2#
3
4# You can set these variables from the command line.
5SPHINXOPTS =
6SPHINXBUILD = sphinx-build
7PAPER =
8BUILDDIR = build
9
10# Internal variables.
11PAPEROPT_a4 = -D latex_paper_size=a4
12PAPEROPT_letter = -D latex_paper_size=letter
13ALLSPHINXOPTS = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
14
15.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest
16
17help:
18 @echo "Please use \`make <target>' where <target> is one of"
19 @echo " html to make standalone HTML files"
20 @echo " dirhtml to make HTML files named index.html in directories"
21 @echo " offhtml to make standalone HTML files without fetching the new theme files"
22 @echo " singlehtml to make a single large HTML file"
23 @echo " pickle to make pickle files"
24 @echo " json to make JSON files"
25 @echo " htmlhelp to make HTML files and a HTML help project"
26 @echo " qthelp to make HTML files and a qthelp project"
27 @echo " devhelp to make HTML files and a Devhelp project"
28 @echo " epub to make an epub"
29 @echo " latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
30 @echo " latexpdf to make LaTeX files and run them through pdflatex"
31 @echo " text to make text files"
32 @echo " man to make manual pages"
33 @echo " changes to make an overview of all changed/added/deprecated items"
34 @echo " linkcheck to check all external links for integrity"
35 @echo " doctest to run all doctests embedded in the documentation (if enabled)"
36
37clean:
38 -rm -rf $(BUILDDIR)/*
39
40html:
41 @echo "Downloading percona-theme ..."
42 @wget -O percona-theme.tar.gz http://percona.com/docs/theme/percona-server/5.6
43 @echo "Extracting theme."
44 @tar -zxf percona-theme.tar.gz
45 @rm -rf source/percona-theme
46 @mv percona-theme source/percona-theme
47 @rm percona-theme.tar.gz
48 @echo "Building html doc"
49
50 $(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
51 @echo
52 @echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
53
54dirhtml:
55 $(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
56 @echo
57 @echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
58
59offhtml:
60 $(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
61 @echo
62 @echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
63
64singlehtml:
65 $(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
66 @echo
67 @echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
68
69pickle:
70 $(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
71 @echo
72 @echo "Build finished; now you can process the pickle files."
73
74json:
75 $(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
76 @echo
77 @echo "Build finished; now you can process the JSON files."
78
79htmlhelp:
80 $(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
81 @echo
82 @echo "Build finished; now you can run HTML Help Workshop with the" \
83 ".hhp project file in $(BUILDDIR)/htmlhelp."
84
85qthelp:
86 $(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
87 @echo
88 @echo "Build finished; now you can run "qcollectiongenerator" with the" \
89 ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
90 @echo "# qcollectiongenerator $(BUILDDIR)/qthelp/PerconaServer.qhcp"
91 @echo "To view the help file:"
92 @echo "# assistant -collectionFile $(BUILDDIR)/qthelp/PerconaServer.qhc"
93
94devhelp:
95 $(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
96 @echo
97 @echo "Build finished."
98 @echo "To view the help file:"
99 @echo "# mkdir -p $$HOME/.local/share/devhelp/PerconaServer"
100 @echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/PerconaServer"
101 @echo "# devhelp"
102
103epub:
104 $(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
105 @echo
106 @echo "Build finished. The epub file is in $(BUILDDIR)/epub."
107
108latex:
109 $(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
110 @echo
111 @echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
112 @echo "Run \`make' in that directory to run these through (pdf)latex" \
113 "(use \`make latexpdf' here to do that automatically)."
114
115latexpdf:
116 $(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
117 @echo "Running LaTeX files through pdflatex..."
118 make -C $(BUILDDIR)/latex all-pdf
119 @echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
120
121text:
122 $(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
123 @echo
124 @echo "Build finished. The text files are in $(BUILDDIR)/text."
125
126man:
127 $(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
128 @echo
129 @echo "Build finished. The manual pages are in $(BUILDDIR)/man."
130
131changes:
132 $(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
133 @echo
134 @echo "The overview file is in $(BUILDDIR)/changes."
135
136linkcheck:
137 $(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
138 @echo
139 @echo "Link check complete; look for any errors in the above output " \
140 "or in $(BUILDDIR)/linkcheck/output.txt."
141
142doctest:
143 $(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
144 @echo "Testing of doctests in the sources finished, look at the " \
145 "results in $(BUILDDIR)/doctest/output.txt."
1460
=== added file 'doc/make.bat'
--- doc/make.bat 1970-01-01 00:00:00 +0000
+++ doc/make.bat 2013-05-22 08:54:39 +0000
@@ -0,0 +1,170 @@
1@ECHO OFF
2
3REM Command file for Sphinx documentation
4
5if "%SPHINXBUILD%" == "" (
6 set SPHINXBUILD=sphinx-build
7)
8set BUILDDIR=build
9set ALLSPHINXOPTS=-d %BUILDDIR%/doctrees %SPHINXOPTS% source
10if NOT "%PAPER%" == "" (
11 set ALLSPHINXOPTS=-D latex_paper_size=%PAPER% %ALLSPHINXOPTS%
12)
13
14if "%1" == "" goto help
15
16if "%1" == "help" (
17 :help
18 echo.Please use `make ^<target^>` where ^<target^> is one of
19 echo. html to make standalone HTML files
20 echo. dirhtml to make HTML files named index.html in directories
21 echo. singlehtml to make a single large HTML file
22 echo. pickle to make pickle files
23 echo. json to make JSON files
24 echo. htmlhelp to make HTML files and a HTML help project
25 echo. qthelp to make HTML files and a qthelp project
26 echo. devhelp to make HTML files and a Devhelp project
27 echo. epub to make an epub
28 echo. latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter
29 echo. text to make text files
30 echo. man to make manual pages
31 echo. changes to make an overview over all changed/added/deprecated items
32 echo. linkcheck to check all external links for integrity
33 echo. doctest to run all doctests embedded in the documentation if enabled
34 goto end
35)
36
37if "%1" == "clean" (
38 for /d %%i in (%BUILDDIR%\*) do rmdir /q /s %%i
39 del /q /s %BUILDDIR%\*
40 goto end
41)
42
43if "%1" == "html" (
44 %SPHINXBUILD% -b html %ALLSPHINXOPTS% %BUILDDIR%/html
45 if errorlevel 1 exit /b 1
46 echo.
47 echo.Build finished. The HTML pages are in %BUILDDIR%/html.
48 goto end
49)
50
51if "%1" == "dirhtml" (
52 %SPHINXBUILD% -b dirhtml %ALLSPHINXOPTS% %BUILDDIR%/dirhtml
53 if errorlevel 1 exit /b 1
54 echo.
55 echo.Build finished. The HTML pages are in %BUILDDIR%/dirhtml.
56 goto end
57)
58
59if "%1" == "singlehtml" (
60 %SPHINXBUILD% -b singlehtml %ALLSPHINXOPTS% %BUILDDIR%/singlehtml
61 if errorlevel 1 exit /b 1
62 echo.
63 echo.Build finished. The HTML pages are in %BUILDDIR%/singlehtml.
64 goto end
65)
66
67if "%1" == "pickle" (
68 %SPHINXBUILD% -b pickle %ALLSPHINXOPTS% %BUILDDIR%/pickle
69 if errorlevel 1 exit /b 1
70 echo.
71 echo.Build finished; now you can process the pickle files.
72 goto end
73)
74
75if "%1" == "json" (
76 %SPHINXBUILD% -b json %ALLSPHINXOPTS% %BUILDDIR%/json
77 if errorlevel 1 exit /b 1
78 echo.
79 echo.Build finished; now you can process the JSON files.
80 goto end
81)
82
83if "%1" == "htmlhelp" (
84 %SPHINXBUILD% -b htmlhelp %ALLSPHINXOPTS% %BUILDDIR%/htmlhelp
85 if errorlevel 1 exit /b 1
86 echo.
87 echo.Build finished; now you can run HTML Help Workshop with the ^
88.hhp project file in %BUILDDIR%/htmlhelp.
89 goto end
90)
91
92if "%1" == "qthelp" (
93 %SPHINXBUILD% -b qthelp %ALLSPHINXOPTS% %BUILDDIR%/qthelp
94 if errorlevel 1 exit /b 1
95 echo.
96 echo.Build finished; now you can run "qcollectiongenerator" with the ^
97.qhcp project file in %BUILDDIR%/qthelp, like this:
98 echo.^> qcollectiongenerator %BUILDDIR%\qthelp\PerconaServer.qhcp
99 echo.To view the help file:
100 echo.^> assistant -collectionFile %BUILDDIR%\qthelp\PerconaServer.ghc
101 goto end
102)
103
104if "%1" == "devhelp" (
105 %SPHINXBUILD% -b devhelp %ALLSPHINXOPTS% %BUILDDIR%/devhelp
106 if errorlevel 1 exit /b 1
107 echo.
108 echo.Build finished.
109 goto end
110)
111
112if "%1" == "epub" (
113 %SPHINXBUILD% -b epub %ALLSPHINXOPTS% %BUILDDIR%/epub
114 if errorlevel 1 exit /b 1
115 echo.
116 echo.Build finished. The epub file is in %BUILDDIR%/epub.
117 goto end
118)
119
120if "%1" == "latex" (
121 %SPHINXBUILD% -b latex %ALLSPHINXOPTS% %BUILDDIR%/latex
122 if errorlevel 1 exit /b 1
123 echo.
124 echo.Build finished; the LaTeX files are in %BUILDDIR%/latex.
125 goto end
126)
127
128if "%1" == "text" (
129 %SPHINXBUILD% -b text %ALLSPHINXOPTS% %BUILDDIR%/text
130 if errorlevel 1 exit /b 1
131 echo.
132 echo.Build finished. The text files are in %BUILDDIR%/text.
133 goto end
134)
135
136if "%1" == "man" (
137 %SPHINXBUILD% -b man %ALLSPHINXOPTS% %BUILDDIR%/man
138 if errorlevel 1 exit /b 1
139 echo.
140 echo.Build finished. The manual pages are in %BUILDDIR%/man.
141 goto end
142)
143
144if "%1" == "changes" (
145 %SPHINXBUILD% -b changes %ALLSPHINXOPTS% %BUILDDIR%/changes
146 if errorlevel 1 exit /b 1
147 echo.
148 echo.The overview file is in %BUILDDIR%/changes.
149 goto end
150)
151
152if "%1" == "linkcheck" (
153 %SPHINXBUILD% -b linkcheck %ALLSPHINXOPTS% %BUILDDIR%/linkcheck
154 if errorlevel 1 exit /b 1
155 echo.
156 echo.Link check complete; look for any errors in the above output ^
157or in %BUILDDIR%/linkcheck/output.txt.
158 goto end
159)
160
161if "%1" == "doctest" (
162 %SPHINXBUILD% -b doctest %ALLSPHINXOPTS% %BUILDDIR%/doctest
163 if errorlevel 1 exit /b 1
164 echo.
165 echo.Testing of doctests in the sources finished, look at the ^
166results in %BUILDDIR%/doctest/output.txt.
167 goto end
168)
169
170:end
0171
=== added directory 'doc/source/diagnostics'
=== added file 'doc/source/diagnostics/innodb_deadlock_count.rst'
--- doc/source/diagnostics/innodb_deadlock_count.rst 1970-01-01 00:00:00 +0000
+++ doc/source/diagnostics/innodb_deadlock_count.rst 2013-05-22 08:54:39 +0000
@@ -0,0 +1,57 @@
1.. _innodb_deadlocks_page:
2
3==========================
4 Count |InnoDB| Deadlocks
5==========================
6
7When running a transactional application you have to live with deadlocks. They are not problematic as long as they do not occur too frequently. The standard ``SHOW INNODB STATUS`` gives information on the latest deadlocks but it is not very useful when you want to know the total number of deadlocks or the number of deadlocks per unit of time.
8
9This change adds a status variable that keeps track of the number of deadlocks since the server startup, opening the way to a better knowledge of your deadlocks.
10
11This feature was provided by Eric Bergen under BSD license (see `InnoDB Deadlock Count Patch <http://ebergen.net/wordpress/2009/08/27/innodb-deadlock-count-patch/>`_).
12
13It adds a new global status variable (:variable:`innodb_deadlocks`) showing the number of deadlocks.*
14
15You can use it with ``SHOW GLOBAL STATUS``, e.g.: ::
16
17 mysql> SHOW GLOBAL STATUS LIKE 'innodb_deadlocks';
18 +------------------+-------+
19 | Variable_name | Value |
20 +------------------+-------+
21 | innodb_deadlocks | 323 |
22 +------------------+-------+
23
24or with ``INFORMATION_SCHEMA``, e.g.: ::
25
26 mysql> SELECT VARIABLE_VALUE FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'innodb_deadlocks';
27 +----------------+
28 | VARIABLE_VALUE |
29 +----------------+
30 | 323 |
31 +----------------+
32
33A deadlock will occur when at least two transactions are mutually waiting for the other to finish, thus creating a circular dependency that lasts until something breaks it. |InnoDB| is quite good at detecting deadlocks and generally returns an error instantly. Most transactional systems have no way to prevent deadlocks from occurring and must be designed to handle them, for instance by retrying the transaction that failed.
34
35
36Version Specific Information
37============================
38
39 * 5.5.8-20.0:
40 Full functionality available.
41
42Status Variables
43================
44
45One new status variable was introduced by this feature.
46
47.. variable:: innodb_deadlocks
48
49 :vartype: LONG
50 :scope: Global
51
52
53Related Reading
54===============
55
56 * `Original post by Eric Bergen <http://ebergen.net/wordpress/2009/08/27/|InnoDB|-deadlock-count-patch/>`_
57
058
=== added file 'doc/source/diagnostics/innodb_show_lock_names.rst'
--- doc/source/diagnostics/innodb_show_lock_names.rst 1970-01-01 00:00:00 +0000
+++ doc/source/diagnostics/innodb_show_lock_names.rst 2013-05-22 08:54:39 +0000
@@ -0,0 +1,24 @@
1.. _innodb_show_lock_names:
2
3=================
4 Show Lock Names
5=================
6
7This feature is currently undocumented except for the following example.
8
9Example: ::
10
11 mysql> SHOW ENGINE INNODB MUTEX;
12 +--------+---------------------------+---------------+
13 | Type | Name | Status |
14 +--------+---------------------------+---------------+
15 | InnoDB | &rseg->mutex | os_waits=210 |
16 | InnoDB | &dict_sys->mutex | os_waits=3 |
17 | InnoDB | &trx_doublewrite->mutex | os_waits=1 |
18 | InnoDB | &log_sys->mutex | os_waits=1197 |
19 | InnoDB | &LRU_list_mutex | os_waits=2 |
20 | InnoDB | &fil_system->mutex | os_waits=5 |
21 | InnoDB | &kernel_mutex | os_waits=242 |
22 | InnoDB | &new_index->lock | os_waits=2 |
23 | InnoDB | &new_index->lock | os_waits=415 |
24 .....
025
=== added file 'doc/source/diagnostics/innodb_show_status.rst'
--- doc/source/diagnostics/innodb_show_status.rst 1970-01-01 00:00:00 +0000
+++ doc/source/diagnostics/innodb_show_status.rst 2013-05-22 08:54:39 +0000
@@ -0,0 +1,475 @@
1.. _innodb_show_status:
2
3======================
4 Show |InnoDB| Status
5======================
6
7This feature reorganizes the output of ``SHOW INNODB STATUS`` for a better readability and prints the amount of memory used by the internal hash tables. In addition, new variables are available to control the output.
8
9This feature modified the ``SHOW INNODB STATUS`` command as follows:
10
11 * ``TRANSACTION`` section was moved to the end of the output, so that important information is not overlooked when the there is a large amount of it.
12
13 * Added two variables to control ``SHOW INNODB STATUS`` information presented (bugfix for `#29123 <http://bugs.mysql.com/bug.php?id=29126>`_):
14
15 * :variable:`innodb_show_verbose_locks` - Whether to show records locked
16
17 * :variable:`innodb_show_locks_held` - Number of locks held to print for each |InnoDB| transaction
18
19 * Added extended information about |InnoDB| internal hash table sizes (in bytes) in the ``BUFFER POOL AND MEMORY`` section; also added buffer pool size in bytes.
20
21 * Added additional LOG section information (beginning in release 5.5.8-20.0).
22
23Version Specific Information
24============================
25
26 * 5.5.8-20.0
27 Added status variables showing information from ``SHOW INNODB STATUS``.
28
29 * 5.5.8-20.0
30 Added additional information in the LOG section.
31
32 * 5.5.10-20.1:
33 Renamed status variable :variable:`innodb_row_lock_numbers` to :variable:`innodb_current_row_locks`.
34
35Other Information
36=================
37
38 * Author / Origin:
39 Baron Schwartz, http://lists.mysql.com/internals/35174
40
41
42System Variables
43================
44
45.. variable:: innodb_show_verbose_locks
46
47 :cli: Yes
48 :conf: Yes
49 :scope: Global
50 :dyn: Yes
51 :vartype: ULONG
52 :default: 0
53 :range: 0 - 1
54
55Specifies to show records locked in ``SHOW INNODB STATUS``. The default is 0, which means only the higher-level information about the lock (which table and index is locked, etc.) is printed. If set to 1, then traditional |InnoDB| behavior is enabled: the records that are locked are dumped to the output.
56
57.. variable:: innodb_show_locks_held
58
59 :cli: Yes
60 :conf: Yes
61 :scope: Global
62 :dyn: Yes
63 :vartype: ULONG
64 :default: 10
65 :range: 0 - 1000
66
67Specifies the number of locks held to print for each |InnoDB| transaction in SHOW INNODB STATUS.
68
69
70Status Variables
71================
72
73The status variables here contain information available in the output of ``SHOW INNODB STATUS``, organized by the sections ``SHOW INNODB STATUS`` displays. If you are familiar with the output of ``SHOW INNODB STATUS``, you will probably already recognize the information these variables contain.
74
75
76BACKGROUND THREAD
77-----------------
78
79The following variables contain information in the BACKGROUND THREAD section of the output from ``SHOW INNODB STATUS``. An example of that output is:
80
81 Insert an example of BACKGROUND THREAD section output here.
82
83.. variable:: innodb_master_thread_1_second_loops
84
85 :version 5.5.8-20.0: Introduced.
86 :vartype: Numeric
87 :scope: Global
88
89.. variable:: innodb_master_thread_10_second_loops
90
91 :version 5.5.8-20.0: Introduced.
92 :vartype: Numeric
93 :scope: Global
94
95.. variable:: innodb_master_thread_background_loops
96
97 :version 5.5.8-20.0: Introduced.
98 :vartype: Numeric
99 :scope: Global
100
101.. variable:: innodb_master_thread_main_flush_loops
102
103 :version 5.5.8-20.0: Introduced.
104 :vartype: Numeric
105 :scope: Global
106
107.. variable:: innodb_master_thread_sleeps
108
109 :version 5.5.8-20.0: Introduced.
110 :vartype: Numeric
111 :scope: Global
112
113.. variable:: innodb_background_log_sync
114
115 :version 5.5.8-20.0: Introduced.
116 :vartype: Numeric
117 :scope: Global
118
119SEMAPHORES
120----------
121
122The following variables contain information in the SEMAPHORES section of the output from ``SHOW INNODB STATUS``. An example of that output is: ::
123
124 ----------
125 SEMAPHORES
126 ----------
127 OS WAIT ARRAY INFO: reservation count 9664, signal count 11182
128 Mutex spin waits 20599, rounds 223821, OS waits 4479
129 RW-shared spins 5155, OS waits 1678; RW-excl spins 5632, OS waits 2592
130 Spin rounds per wait: 10.87 mutex, 15.01 RW-shared, 27.19 RW-excl
131
132.. variable:: innodb_mutex_os_waits
133
134 :version 5.5.8-20.0: Introduced.
135 :vartype: Numeric
136 :scope: Global
137
138.. variable:: innodb_mutex_spin_rounds
139
140 :version 5.5.8-20.0: Introduced.
141 :vartype: Numeric
142 :scope: Global
143
144.. variable:: innodb_mutex_spin_waits
145
146 :version 5.5.8-20.0: Introduced.
147 :vartype: Numeric
148 :scope: Global
149
150.. variable:: innodb_s_lock_os_waits
151
152 :version 5.5.8-20.0: Introduced.
153 :vartype: Numeric
154 :scope: Global
155
156.. variable:: innodb_s_lock_spin_rounds
157
158 :version 5.5.8-20.0: Introduced.
159 :vartype: Numeric
160 :scope: Global
161
162.. variable:: innodb_s_lock_spin_waits
163
164 :version 5.5.8-20.0: Introduced.
165 :vartype: Numeric
166 :scope: Global
167
168.. variable:: innodb_x_lock_os_waits
169
170 :version 5.5.8-20.0: Introduced.
171 :vartype: Numeric
172 :scope: Global
173
174.. variable:: innodb_x_lock_spin_rounds
175
176 :version 5.5.8-20.0: Introduced.
177 :vartype: Numeric
178 :scope: Global
179
180.. variable:: innodb_x_lock_spin_waits
181
182 :version 5.5.8-20.0: Introduced.
183 :vartype: Numeric
184 :scope: Global
185
186INSERT BUFFER AND ADAPTIVE HASH INDEX
187-------------------------------------
188
189The following variables contain information in the INSERT BUFFER AND ADAPTIVE HASH INDEX section of the output from SHOW |InnoDB| STATUS. An example of that output is: ::
190
191 -------------------------------------
192 INSERT BUFFER AND ADAPTIVE HASH INDEX
193 -------------------------------------
194 Ibuf: size 1, free list len 6089, seg size 6091,
195 44497 inserts, 44497 merged recs, 8734 merges
196 Hash table size 276707, node heap has 1 buffer(s)
197 0.00 hash searches/s, 0.00 non-hash searches/s
198
199.. variable:: innodb_ibuf_discarded_delete_marks
200
201 :version 5.5.8-20.0: Introduced.
202 :vartype: Numeric
203 :scope: Global
204
205.. variable:: innodb_ibuf_discarded_deletes
206
207 :version 5.5.8-20.0: Introduced.
208 :vartype: Numeric
209 :scope: Global
210
211.. variable:: innodb_ibuf_discarded_inserts
212
213 :version 5.5.8-20.0: Introduced.
214 :vartype: Numeric
215 :scope: Global
216
217.. variable:: innodb_ibuf_free_list
218
219 :version 5.5.8-20.0: Introduced.
220 :vartype: Numeric
221 :scope: Global
222
223.. variable:: innodb_ibuf_merged_delete_marks
224
225 :version 5.5.8-20.0: Introduced.
226 :vartype: Numeric
227 :scope: Global
228
229.. variable:: innodb_ibuf_merged_deletes
230
231 :version 5.5.8-20.0: Introduced.
232 :vartype: Numeric
233 :scope: Global
234
235.. variable:: innodb_ibuf_merged_inserts
236
237 :version 5.5.8-20.0: Introduced.
238 :vartype: Numeric
239 :scope: Global
240
241.. variable:: innodb_ibuf_merges
242
243 :version 5.5.8-20.0: Introduced.
244 :vartype: Numeric
245 :scope: Global
246
247.. variable:: innodb_ibuf_segment_size
248
249 :version 5.5.8-20.0: Introduced.
250 :vartype: Numeric
251 :scope: Global
252
253.. variable:: innodb_ibuf_size
254
255 :version 5.5.8-20.0: Introduced.
256 :vartype: Numeric
257 :scope: Global
258
259.. variable:: innodb_adaptive_hash_cells
260
261 :version 5.5.8-20.0: Introduced.
262 :vartype: Numeric
263 :scope: Global
264
265.. variable:: innodb_adaptive_hash_heap_buffers
266
267 :version 5.5.8-20.0: Introduced.
268 :vartype: Numeric
269 :scope: Global
270
271.. variable:: innodb_adaptive_hash_hash_searches
272
273 :version 5.5.8-20.0: Introduced.
274 :vartype: Numeric
275 :scope: Global
276
277.. variable:: innodb_adaptive_hash_non_hash_searches
278
279 :version 5.5.8-20.0: Introduced.
280 :vartype: Numeric
281 :scope: Global
282
283LOG
284---
285
286The following variables contain information in the LOG section of the output from ``SHOW INNODB STATUS``. An example of that output is: ::
287
288 ---
289 LOG
290 ---
291 Log sequence number 28219393219
292 Log flushed up to 28219393219
293 Last checkpoint at 28212583337
294 Max checkpoint age 7782360
295 Checkpoint age target 7539162
296 Modified age 6809882
297 Checkpoint age 6809882
298 0 pending log writes, 0 pending chkp writes
299 8570 log i/o's done, 2000.00 log i/o's/second
300
301.. variable:: innodb_lsn_current
302
303 :version 5.5.8-20.0: Introduced.
304 :vartype: Numeric
305 :scope: Global
306
307.. variable:: innodb_lsn_flushed
308
309 :version 5.5.8-20.0: Introduced.
310 :vartype: Numeric
311 :scope: Global
312
313.. variable:: innodb_lsn_last_checkpoint
314
315 :version 5.5.8-20.0: Introduced.
316 :vartype: Numeric
317 :scope: Global
318
319.. variable:: innodb_checkpoint_age
320
321 :version 5.5.8-20.0: Introduced.
322 :vartype: Numeric
323 :scope: Global
324
325.. variable:: innodb_checkpoint_max_age
326
327 :version 5.5.8-20.0: Introduced.
328 :vartype: Numeric
329 :scope: Global
330
331.. variable:: innodb_checkpoint_target_age
332
333 :version 5.5.8-20.0: Introduced.
334 :vartype: Numeric
335 :scope: Global
336
337BUFFER POOL AND MEMORY
338----------------------
339
340The following variables contain information in the BUFFER POOL AND MEMORY section of the output from ``SHOW INNODB STATUS``. An example of that output is: ::
341
342 ----------------------
343 BUFFER POOL AND MEMORY
344 ----------------------
345 Total memory allocated 137625600; in additional pool allocated 0
346 Internal hash tables (constant factor + variable factor)
347 Adaptive hash index 3774352 (2213656 + 1560696)
348 Page hash 139144
349 Dictionary cache 629811 (554864 + 74947)
350 File system 83536 (82672 + 864)
351 Lock system 380792 (332872 + 47920)
352 Recovery system 0 (0 + 0)
353 Threads 84040 (82696 + 1344)
354 Dictionary memory allocated 74947
355 Buffer pool size 8192
356 Buffer pool size, bytes 134217728
357 Free buffers 0
358 Database pages 8095
359 Old database pages 2968
360 Modified db pages 5914
361 Pending reads 0
362 Pending writes: LRU 0, flush list 129, single page 0
363 Pages made young 372084, not young 0
364 2546000.00 youngs/s, 0.00 non-youngs/s
365 Pages read 103356, created 154787, written 979572
366 469000.00 reads/s, 78000.00 creates/s, 138000.00 writes/s
367 Buffer pool hit rate 994 / 1000, young-making rate 34 / 1000 not 0 / 1000
368 Pages read ahead 0.00/s, evicted without access 15000.00/s
369
370.. variable:: innodb_mem_adaptive_hash
371
372 :version 5.5.8-20.0: Introduced.
373 :vartype: Numeric
374 :scope: Global
375
376.. variable:: innodb_mem_dictionary
377
378 :version 5.5.8-20.0: Introduced.
379 :vartype: Numeric
380 :scope: Global
381
382.. variable:: innodb_mem_total
383
384 :version 5.5.8-20.0: Introduced.
385 :vartype: Numeric
386 :scope: Global
387
388.. variable:: innodb_buffer_pool_pages_LRU_flushed
389
390 :version 5.5.8-20.0: Introduced.
391 :vartype: Numeric
392 :scope: Global
393
394.. variable:: innodb_buffer_pool_pages_made_not_young
395
396 :version 5.5.8-20.0: Introduced.
397 :vartype: Numeric
398 :scope: Global
399
400.. variable:: innodb_buffer_pool_pages_made_young
401
402 :version 5.5.8-20.0: Introduced.
403 :vartype: Numeric
404 :scope: Global
405
406.. variable:: innodb_buffer_pool_pages_old
407
408 :version 5.5.8-20.0: Introduced.
409 :vartype: Numeric
410 :scope: Global
411
412TRANSACTIONS
413------------
414
415The following variables contain information in the TRANSACTIONS section of the output from ``SHOW INNODB STATUS``. An example of that output is: ::
416
417 ------------
418 TRANSACTIONS
419 ------------
420 Trx id counter F561FD
421 Purge done for trx's n:o < F561EB undo n:o < 0
422 History list length 19
423 LIST OF TRANSACTIONS FOR EACH SESSION:
424 ---TRANSACTION 0, not started, process no 993, OS thread id 140213152634640
425 mysql thread id 15933, query id 32109 localhost root
426 show innodb status
427 ---TRANSACTION F561FC, ACTIVE 29 sec, process no 993, OS thread id 140213152769808 updating or deleting
428 mysql tables in use 1, locked 1
429
430.. variable:: innodb_history_list_length
431
432 :version 5.5.8-20.0: Introduced.
433 :vartype: Numeric
434 :scope: Global
435
436.. variable:: innodb_max_trx_id
437
438 :version 5.5.8-20.0: Introduced.
439 :vartype: Numeric
440 :scope: Global
441
442.. variable:: innodb_oldest_view_low_limit_trx_id
443
444 :version 5.5.8-20.0: Introduced.
445 :vartype: Numeric
446 :scope: Global
447
448.. variable:: innodb_purge_trx_id
449
450 :version 5.5.8-20.0: Introduced.
451 :vartype: Numeric
452 :scope: Global
453
454.. variable:: innodb_purge_undo_no
455
456 :version 5.5.8-20.0: Introduced.
457 :vartype: Numeric
458 :scope: Global
459
460.. variable:: innodb_current_row_locks
461
462 :version 5.5.8-20.0: Introduced.
463 :version 5.5.10-20.1: Renamed.
464 :vartype: Numeric
465 :scope: Global
466
467 This variable was named :variable:`innodb_row_lock_numbers` in release 5.5.8-20.0.
468
469
470Other reading
471=============
472
473 * `SHOW INNODB STATUS walk through <http://www.mysqlperformanceblog.com/2006/07/17/show-innodb-status-walk-through/>`_
474
475 * `Table locks in SHOW INNODB STATUS <http://www.mysqlperformanceblog.com/2010/06/08/table-locks-in-show-innodb-status/>`_
0476
=== added file 'doc/source/diagnostics/misc_info_schema_tables.rst'
--- doc/source/diagnostics/misc_info_schema_tables.rst 1970-01-01 00:00:00 +0000
+++ doc/source/diagnostics/misc_info_schema_tables.rst 2013-03-05 12:46:43 +0000
@@ -0,0 +1,48 @@
1.. _misc_info_schema_tables:
2
3=================================
4 Misc. INFORMATION_SCHEMA Tables
5=================================
6
7This page lists the ``INFORMATION_SCHEMA`` tables added to standard |MySQL| by |Percona Server| that don't exist elsewhere in the documentation.
8
9.. _temp_tables:
10
11Temporary tables
12================
13
14 Only the temporary tables that were explicitly created with `CREATE TEMPORARY TABLE` or `ALTER TABLE` are shown, and not the ones created to process complex queries.
15
16.. table:: INFORMATION_SCHEMA.GLOBAL_TEMPORARY_TABLES
17
18 :version 5.6.5-60.0: Feature introduced
19 :column SESSION_ID: |MySQL| connection id
20 :column TABLE_SCHEMA: Schema in which the temporary table is created
21 :column TABLE_NAME: Name of the temporary table
22 :column ENGINE: Engine of the temporary table
23 :column NAME: Internal name of the temporary table
24 :column TABLE_ROWS: Number of rows of the temporary table
25 :column AVG_ROW_LENGTH: Average row length of the temporary table
26 :column DATA_LENGTH: Size of the data (Bytes)
27 :column INDEX_LENGTH: Size of the indexes (Bytes)
28 :column CREATE_TIME: Date and time of creation of the temporary table
29 :column UPDATE_TIME: Date and time of the latest update of the temporary table
30
31This table holds information on the temporary tables existing for all connections. You don't need the ``SUPER`` privilege to query this table.
32
33.. table:: INFORMATION_SCHEMA.TEMPORARY_TABLES
34
35 :version 5.6.5-60.0: Feature introduced
36 :column SESSION_ID: |MySQL| connection id
37 :column TABLE_SCHEMA: Schema in which the temporary table is created
38 :column TABLE_NAME: Name of the temporary table
39 :column ENGINE: Engine of the temporary table
40 :column NAME: Internal name of the temporary table
41 :column TABLE_ROWS: Number of rows of the temporary table
42 :column AVG_ROW_LENGTH: Average row length of the temporary table
43 :column DATA_LENGTH: Size of the data (Bytes)
44 :column INDEX_LENGTH: Size of the indexes (Bytes)
45 :column CREATE_TIME: Date and time of creation of the temporary table
46 :column UPDATE_TIME: Date and time of the latest update of the temporary table
47
48This table holds information on the temporary tables existing for the running connection.
049
=== added file 'doc/source/diagnostics/mysql_syslog.rst'
--- doc/source/diagnostics/mysql_syslog.rst 1970-01-01 00:00:00 +0000
+++ doc/source/diagnostics/mysql_syslog.rst 2013-05-22 08:54:39 +0000
@@ -0,0 +1,43 @@
1.. _mysql_syslog:
2
3======================================
4 Log All Client Commands (``syslog``)
5======================================
6
7When enabled, this feature causes all commands run by the command line client to be logged to syslog. If you want to enable this option permanently, add it to the [mysql] group in my.cnf.
8
9Version Specific Information
10============================
11
12 * :rn:`5.5.8-20.0`:
13 Full functionality available.
14
15Other Information
16=================
17
18 * Author / Origin:
19 Percona
20
21Client Variables
22================
23
24.. variable:: syslog
25
26 :cli: Yes
27 :conf: Yes
28 :server: No
29 :scope: Global
30 :dyn: Yes
31 :vartype: Boolean
32 :default: OFF
33 :range: ON/OFF
34
35The variable enables (ON)/disables (OFF) logging to syslog.
36
37
38Other Reading
39=============
40
41 * http://en.wikipedia.org/wiki/Syslog
42
43 * http://tools.ietf.org/html/rfc5424
044
=== added file 'doc/source/diagnostics/process_list.rst'
--- doc/source/diagnostics/process_list.rst 1970-01-01 00:00:00 +0000
+++ doc/source/diagnostics/process_list.rst 2013-03-05 12:46:43 +0000
@@ -0,0 +1,53 @@
1.. _process_list:
2
3=============
4Process List
5=============
6
7This page describes Percona changes to both the standard |MySQL| ``SHOW PROCESSLIST`` command and the standard |MySQL| ``INFORMATION_SCHEMA`` table ``PROCESSLIST``.
8
9The changes that have been made as of version 5.6 of the server are:
10
11 * :table:`PROCESSLIST` table:
12
13 * added column ``TIME_MS``
14
15Version Specific Information
16============================
17
18 * :rn:`5.6.5-60.0`:
19
20 * Added column ``TIME_MS`` to table ``PROCESSLIST``.
21
22
23INFORMATION_SCHEMA Tables
24=========================
25
26.. table:: INFORMATION_SCHEMA.PROCESSLIST
27
28 This table implements modifications to the standard |MySQL| ``INFORMATION_SCHEMA`` table ``PROCESSLIST``.
29
30 :column ID: The connection identifier.
31 :column USER: The |MySQL| user who issued the statement.
32 :column HOST: The host name of the client issuing the statement.
33 :column DB: The default database, if one is selected, otherwise NULL.
34 :column COMMAND: The type of command the thread is executing.
35 :column TIME: The time in seconds that the thread has been in its current state.
36 :column STATE: An action, event, or state that indicates what the thread is doing.
37 :column INFO: The statement that the thread is executing, or NULL if it is not executing any statement.
38 :column TIME_MS: The time in milliseconds that the thread has been in its current state.
39
40
41Example Output
42==============
43
44Table :table:`PROCESSLIST`: ::
45
46 mysql> SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST;
47
48 +----+------+-----------+--------------------+---------+------+-----------+----------------------------------------------+---------+
49 | ID | USER | HOST | DB | COMMAND | TIME | STATE | INFO | TIME_MS |
50 +----+------+-----------+--------------------+---------+------+-----------+----------------------------------------------+---------+
51 | 5 | root | localhost | information_schema | Query | 0 | executing | select * from information_schema.PROCESSLIST | 0 |
52 +----+------+-----------+--------------------+---------+------+-----------+----------------------------------------------+---------+
53
054
=== added file 'doc/source/diagnostics/show_engines.rst'
--- doc/source/diagnostics/show_engines.rst 1970-01-01 00:00:00 +0000
+++ doc/source/diagnostics/show_engines.rst 2013-05-22 08:54:39 +0000
@@ -0,0 +1,40 @@
1.. _show_engines:
2
3======================
4 Show Storage Engines
5======================
6
7This feature changes the comment field displayed when the ``SHOW STORAGE ENGINES`` command is executed and |XtraDB| is the storage engine.
8
9Before the Change: ::
10
11 mysql> show storage engines;
12 +------------+---------+----------------------------------------------------------------+--------------+------+------------+
13 | Engine | Support | Comment | Transactions | XA | Savepoints |
14 +------------+---------+----------------------------------------------------------------+--------------+------+------------+
15 | InnoDB | YES | Supports transactions, row-level locking, and foreign keys | YES | YES | YES |
16 ...
17 +------------+---------+----------------------------------------------------------------+--------------+------+------------+
18
19After the Change: ::
20
21 mysql> show storage engines;
22 +------------+---------+----------------------------------------------------------------------------+--------------+------+------------+
23 | Engine | Support | Comment | Transactions | XA | Savepoints |
24 +------------+---------+----------------------------------------------------------------------------+--------------+------+------------+
25 | InnoDB | YES | Percona-XtraDB, Supports transactions, row-level locking, and foreign keys | YES | YES | YES |
26 ...
27 +------------+---------+----------------------------------------------------------------------------+--------------+------+------------+
28
29Version-Specific Information
30============================
31
32 * 5.5.8-20.0:
33 Full functionality available.
34
35Other Information
36=================
37
38 * Author / Origin:
39 Percona
40
041
=== added file 'doc/source/diagnostics/slow_extended_55.rst'
--- doc/source/diagnostics/slow_extended_55.rst 1970-01-01 00:00:00 +0000
+++ doc/source/diagnostics/slow_extended_55.rst 2013-05-22 08:54:39 +0000
@@ -0,0 +1,377 @@
1.. _slow_extended_55:
2
3================
4 Slow Query Log
5================
6
7This feature adds microsecond time resolution and additional statistics to the slow query log output. It lets you enable or disable the slow query log at runtime, adds logging for the slave SQL thread, and adds fine-grained control over what and how much to log into the slow query log.
8
9The ability to log queries with microsecond precision is essential for measuring the work the |MySQL| server performs. The standard slow query log in |MySQL| 5.0 has only 1-second granularity, which is too coarse for all but the slowest queries. |MySQL| 5.1 has microsecond resolution, but does not have the extra information about query execution that is included in the |Percona Server|.
10
11You can use *Percona-Toolkit*'s `pt-query-digest <http://www.percona.com/doc/percona-toolkit/2.1/pt-query-digest.html>`_ tool to aggregate similar queries together and report on those that consume the most execution time.
12
13
14Version Specific Information
15============================
16
17 * 5.5.8-20.0:
18 Added values ``profiling`` and ``profiling_use_getrusage`` to variable log_slow_verbosity.
19
20 * 5.5.10-20.1:
21 * Renamed variable :variable:`slow_query_log_timestamp_always` to :variable:`slow_query_log_timestamp_always`.
22
23 * Renamed variable :variable:`slow_query_log_microseconds_timestamp` to :variable:`slow_query_log_timestamp_precision`.
24
25 * Renamed variable :variable:`use_global_log_slow_control` to :variable:`slow_query_log_use_global_control`.
26
27Other Information
28=================
29
30 * Author / Origin:
31 Maciej Dobrzanski, Percona
32
33System Variables
34================
35
36.. variable:: log_slow_admin_statements
37
38 :cli: Yes
39 :conf: Yes
40 :scope: Global
41 :dyn: yes
42
43When this variable is enabled, administrative statements will be logged to the slow query log. Upstream version of the |MySQL| server has implemented command line option with same name. Significant difference is that this feature is implemented as variable in |Percona Server|, that means it can be enabled/disabled dynamically without restarting the server.
44
45.. variable:: log_slow_filter
46
47 :cli: Yes
48 :conf: Yes
49 :scope: Global, Session
50 :dyn: Yes
51
52Filters 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:
53
54 * ``qc_miss``:
55 The query was not found in the query cache.
56
57 * ``full_scan``:
58 The query performed a full table scan.
59
60 * ``full_join``:
61 The query performed a full join (a join without indexes).
62
63 * ``tmp_table``:
64 The query created an implicit internal temporary table.
65
66 * ``tmp_table_on_disk``:
67 The query``s temporary table was stored on disk.
68
69 * ``filesort``:
70 The query used a filesort.
71
72 * ``filesort_on_disk``:
73 The filesort was performed on disk.
74
75Values are OR'ed together. If the string is empty, then the filter is disabled. If it is not empty, then queries will only be logged to the slow log if their execution plan matches one of the types of plans present in the filter.
76
77For example, to log only queries that perform a full table scan, set the value to ``full_scan``. To log only queries that use on-disk temporary storage for intermediate results, set the value to ``tmp_table_on_disk,filesort_on_disk``.
78
79.. variable:: log_slow_rate_type
80
81 :cli: Yes
82 :conf: Yes
83 :scope: Global
84 :dyn: Yes
85 :vartype: Enumerated
86 :default: ``session``
87 :range: ``session``, ``query``
88
89Specifies semantic of :variable:`log_slow_rate_limit` - ``session`` or ``query``.
90
91.. variable:: log_slow_rate_limit
92
93 :cli: Yes
94 :conf: Yes
95 :scope: Global, session
96 :dyn: Yes
97
98Behavior of this variable depends from :variable:`log_slow_rate_type`.
99
100Specifies that only a fraction of ``session/query`` should be logged. Logging is enabled for every nth ``session/query``. By default, n is 1, so logging is enabled for every ``session/query``. Please note: when :variable:`log_slow_rate_type` is ``session`` rate limiting is disabled for the replication thread.
101
102Logging all queries might consume I/O bandwidth and cause the log file to grow large.
103 * When :variable:`log_slow_rate_type` is ``session``, this option lets you log full sessions, so you have complete records of sessions for later analysis; but you can rate-limit the number of sessions that are logged. Note that this feature will not work well if your application uses any type of connection pooling or persistent connections. Note that you change :variable:`log_slow_rate_limit` in ``session`` mode, you should reconnect for get effect.
104
105 * When :variable:`log_slow_rate_type` is ``query``, this option lets you log just some queries for later analysis. For example, if you set the value to 100, then one percona of queryies will logged.
106
107Note that every query has global unique ``query_id`` and every connection can has it own (session) :variable:``log_slow_rate_limit``.
108Decision "log or no" calculated in following manner:
109
110 * if ``log_slow_rate_limit`` is 0 - log every query
111
112 * If ``log_slow_rate_limit`` > 0 - log query when (``query_id`` % ``log_slow_rate_limit``) is zero.
113
114This allows flexible setup logging behavior.
115
116For example, if you set the value to 100, then one percent of ``sessions/queries`` will be logged.
117
118.. variable:: log_slow_slave_statements
119
120 :cli: Yes
121 :conf: Yes
122 :scope: Global, session
123 :dyn: Yes (in 5.1 releases only)
124
125Specifies that slow queries replayed by the slave SQL thread on a |MySQL| slave will be logged. Upstream version of the |MySQL| server has implemented command line option with same name. Significant difference is that this feature is implemented as variable in |Percona Server|, that means it can be enabled/disabled dynamically without restarting the server.
126
127To start the logging from the slave thread, you should change the global value: set global :variable:`log_slow_slave_statements` ``=ON``; and then execute: ``STOP SLAVE; START SLAVE;``. This will destroy and recreate the slave SQL thread, so it will see the newly set global value.
128
129To stop the logging from the slave thread, you should just change the global value: set global :variable:`log_slow_slave_statements` ``=OFF``; the logging stops immediately.
130
131
132.. variable:: log_slow_sp_statements
133
134 :cli: Yes
135 :conf: Yes
136 :scope: Global
137 :dyn: Yes
138 :vartype: Boolean
139 :default: TRUE
140 :range: TRUE/FALSE
141
142If ``TRUE``, statements executed by stored procedures are logged to the slow if it is open.
143
144.. note::
145
146 Support for logging stored procedures doesn't involve triggers, so they won't be logged even if this feature is enabled.
147
148.. variable:: log_slow_verbosity
149
150 :version 5.5.8-20.0: Added ``profiling`` and ``profiling_use_getrusage``
151 :cli: Yes
152 :conf: Yes
153 :scope: Global, session
154 :dyn: Yes
155
156Specifies how much information to include in your slow log. The value is a comma-delimited string, and can contain any combination of the following values:
157
158 * ``microtime``:
159 Log queries with microsecond precision.
160
161 * ``query_plan``:
162 Log information about the query's execution plan.
163
164 * ``innodb``:
165 Log |InnoDB| statistics.
166
167 * ``minimal``:
168 Equivalent to enabling just ``microtime``.
169
170 * ``standard``:
171 Equivalent to enabling ``microtime,innodb``.
172
173 * ``full``:
174 Equivalent to all other values OR'ed together.
175
176 * ``profiling``:
177 Enables profiling of all queries in all connections.
178
179 * ``profiling_use_getrusage``:
180 Enables usage of the getrusage function.
181
182Values are OR'ed together.
183
184For example, to enable microsecond query timing and |InnoDB| statistics, set this option to ``microtime,innodb`` or ``standard``. To turn all options on, set the option to ``full``.
185
186.. variable:: slow_query_log_timestamp_always
187
188 :version 5.5.10-20.1: Introduced (renamed from :variable:`log_slow_timestamp_every`)
189 :cli: Yes
190 :conf: Yes
191 :scope: Global
192 :dyn: Yes
193 :vartype: Boolean
194 :default: FALSE
195 :range: TRUE/FALSE
196
197If ``TRUE``, a timestamp is printed on every slow log record. Multiple records may have the same time.
198
199.. variable:: slow_query_log_timestamp_precision
200
201 :version 5.5.10-20.1: Introduced (renamed from ``slow_query_log_microseconds_timestamp``)
202 :cli: Yes
203 :conf: Yes
204 :scope: Global
205 :dyn: Yes
206 :vartype: Enumerated
207 :default: ``second``
208 :range: ``second``, ``microsecond``
209
210Normally, entries to the slow query log are in seconds precision, in this format: ::
211
212 # Time: 090402 9:23:36 # User@Host: XXX @ XXX [10.X.X.X]
213
214If :variable:`slow_query_log_timestamp_precision` ``=microsecond``, entries to the slow query log are in microsecond precision, in this format: ::
215
216 # Time: 090402 9:23:36.123456 # User@Host: XXX @ XXX [10.X.X.X]
217
218.. variable:: slow_query_log_use_global_control
219
220 :cli: Yes
221 :conf: Yes
222 :scope: Global
223 :dyn: Yes
224 :default: None
225 :version 5.5.10-20.1: Introduced (renamed from :variable:`log_slow_timestamp_every`)
226
227Specifies which variables have global scope instead of local. Value is a “flag” variable - you can specify multiple values separated by commas
228
229 * ``none``:
230 All variables use local scope
231
232 * ``log_slow_filter``:
233 Global variable :variable:`log_slow_filter` has effect (instead of local)
234
235 * ``log_slow_rate_limit``:
236 Global variable :variable:`log_slow_rate_limit` has effect (instead of local)
237
238 * ``log_slow_verbosity``:
239 Global variable :variable:`log_slow_verbosity` has effect (instead of local)
240
241 * ``long_query_time``:
242 Global variable :variable:`long_query_time` has effect (instead of local)
243
244 * ``min_examined_row_limit``:
245 Global variable ``min_examined_row_limit`` has effect (instead of local)
246
247 * ``all``
248 Global variables has effect (instead of local)
249
250**NOTE:** This variable has been renamed from :variable:`log_slow_timestamp_every` since 5.5.10-20.1.
251
252
253Other Information
254=================
255
256Changes to the Log Format
257-------------------------
258
259The feature adds more information to the slow log output. Here is a sample log entry: ::
260
261 # User@Host: mailboxer[mailboxer] @ [192.168.10.165]
262 # Thread_id: 11167745 Schema: board
263 # QC_Hit: No Full_scan: No Full_join: No Tmp_table: Yes Disk_tmp_table: No
264 # Filesort: Yes Disk_filesort: No Merge_passes: 0
265 # Query_time: 0.000659 Lock_time: 0.000070 Rows_sent: 0 Rows_examined: 30 Rows_affected: 0 Rows_read: 30
266 # innodb_IO_r_ops: 1 innodb_IO_r_bytes: 16384 innodb_IO_r_wait: 0.028487
267 # innodb_rec_lock_wait: 0.000000 innodb_queue_wait: 0.000000
268 # innodb_pages_distinct: 5
269 select count(distinct author_id) from art87.article87 force index (forum_id) where forum_id = 240215 and thread_id = ``710575``
270
271Another example (:variable:`log_slow_verbosity` ``=profiling``): ::
272
273 # Query_time: 4.555235 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 Rows_affected: 0 Rows_read: 1
274 # 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
275 # Profile_total: 4.555405 Profile_total_cpu: 0.000000
276 insert into teee4 select * from teee4 limit 10000000;
277
278Connection and Schema Identifier
279--------------------------------
280
281Each slow log entry now contains a connection identifier, so you can trace all the queries coming from a single connection. This is the same value that is shown in the Id column in ``SHOW FULL PROCESSLIST`` or returned from the ``CONNECTION_ID()`` function.
282
283Each entry also contains a schema name, so you can trace all the queries whose default database was set to a particular schema. ::
284
285 # Thread_id: 11167745 Schema: board
286
287Microsecond Time Resolution and Extra Row Information
288-----------------------------------------------------
289
290This is the original functionality offered by the ``microslow`` feature. ``Query_time`` and ``Lock_time`` are logged with microsecond resolution.
291
292The 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, ::
293
294 # Query_time: 0.000659 Lock_time: 0.000070 Rows_sent: 0 Rows_examined: 30 Rows_affected: 0 Rows_read: 30
295
296Values and context:
297
298 * ``Rows_examined``:
299 Number of rows scanned - ``SELECT``
300
301 * ``Rows_affected``:
302 Number of rows changed - ``UPDATE``, ``DELETE``, ``INSERT``
303
304 * ``Rows_read``:
305 Number of rows read - ``UPDATE``, ``DELETE``, ``INSERT``
306
307Memory Footprint
308----------------
309
310The 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. ::
311
312 # Bytes_sent: 8053 Tmp_tables: 1 Tmp_disk_tables: 0 Tmp_table_sizes: 950528
313
314Values and context:
315
316 * ``Bytes_sent``:
317 The amount of bytes sent for the result of the query
318
319 * ``Tmp_tables``:
320 Number of temporary tables created on memory for the query
321
322 * ``Tmp_disk_tables``:
323 Number of temporary tables created on disk for the query
324
325 * ``Tmp_table_sizes``:
326 Total Size in bytes for all temporary tables used in the query
327
328
329Query Plan Information
330----------------------
331
332Each 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. ::
333
334 # QC_Hit: No Full_scan: No Full_join: No Tmp_table: Yes Disk_tmp_table: No
335 # Filesort: Yes Disk_filesort: No Merge_passes: 0
336
337The values and their meanings are documented with the :variable:`log_slow_filter` option.
338
339|InnoDB| Usage Information
340--------------------------
341
342The 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. ::
343
344 # innodb_IO_r_ops: 1 innodb_IO_r_bytes: 16384 innodb_IO_r_wait: 0.028487
345 # innodb_rec_lock_wait: 0.000000 innodb_queue_wait: 0.000000
346 # innodb_pages_distinct: 5
347
348Values:
349
350 * ``innodb_IO_r_ops``:
351 Counts the number of page read operations scheduled. The actual number of read operations may be different, but since this can be done asynchronously, there is no good way to measure it.
352
353 * ``innodb_IO_r_bytes``:
354 Similar to innodb_IO_r_ops, but the unit is bytes.
355
356 * ``innodb_IO_r_wait``:
357 Shows how long (in seconds) it took |InnoDB| to actually read the data from storage.
358
359 * ``innodb_rec_lock_wait``:
360 Shows how long (in seconds) the query waited for row locks.
361
362 * ``innodb_queue_wait``:
363 Shows how long (in seconds) the query spent either waiting to enter the |InnoDB| queue or inside that queue waiting for execution.
364
365 * ``innodb_pages_distinct``:
366 Counts approximately the number of unique pages the query accessed. The approximation is based on a small hash array representing the entire buffer pool, because it could take a lot of memory to map all the pages. The inaccuracy grows with the number of pages accessed by a query, because there is a higher probability of hash collisions.
367
368If the query did not use |InnoDB| tables, that information is written into the log instead of the above statistics.
369
370Related Reading
371===============
372
373 * http://www.mysqlperformanceblog.com/2009/02/10/impact-of-logging-on-mysql%E2%80%99s-performance/
374
375 * `log_slow_filter Usage <http://www.mysqlperformanceblog.com/2008/09/22/finding-what-created_tmp_disk_tables-with-log_slow_filter/>`_
376
377 * `Blueprint in Launchpad <https://blueprints.launchpad.net/percona-server/+spec/microseconds-in-query-log>`_
0378
=== added file 'doc/source/diagnostics/thread_based_profiling.rst'
--- doc/source/diagnostics/thread_based_profiling.rst 1970-01-01 00:00:00 +0000
+++ doc/source/diagnostics/thread_based_profiling.rst 2013-05-22 08:54:39 +0000
@@ -0,0 +1,17 @@
1.. _thread_based_profiling:
2
3=========================
4 Thread Based Profiling
5=========================
6
7|Percona Server| now uses thread based profiling by default, instead of process based profiling. This was implemented because with process based profiling, threads on the server, other than the one being profiled, can affect the profiling information.
8
9Thread based profiling is using the information provided by the kernel `getrusage <http://kernel.org/doc/man-pages/online/pages/man2/getrusage.2.html>`_ function. Since the 2.6.26 kernel version, thread based resource usage is available with the **RUSAGE_THREAD**. This means that the thread based profiling will be used if you're running the 2.6.26 kernel or newer, or if the **RUSAGE_THREAD** has been ported back.
10
11This feature is enabled by default if your system supports it, in other cases it uses process based profiling.
12
13Version Specific Information
14============================
15
16 * :rn:`5.5.25a-27.1`:
17 Thread based profiling introduced
018
=== added file 'doc/source/diagnostics/user_stats.rst'
--- doc/source/diagnostics/user_stats.rst 1970-01-01 00:00:00 +0000
+++ doc/source/diagnostics/user_stats.rst 2013-05-22 08:54:39 +0000
@@ -0,0 +1,242 @@
1.. _user_stats:
2
3=================
4 User Statistics
5=================
6
7This feature adds several ``INFORMATION_SCHEMA`` tables, several commands, and the userstat variable. The tables and commands can be used to understand the server activity better and identify the source of the load.
8
9The functionality is disabled by default, and must be enabled by setting ``userstat`` to ``ON``. It works by keeping several hash tables in memory. To avoid contention over global mutexes, each connection has its own local statistics, which are occasionally merged into the global statistics, and the local statistics are then reset to 0.
10
11
12Version Specific Information
13============================
14
15 * :rn:`5.5.10-20.1`:
16 Renamed variable :variable:`userstat_running` to :variable:`userstat`.
17
18Other Information
19=================
20
21 * Author/Origin:
22 *Google*; *Percona* added the ``INFORMATION_SCHEMA`` tables and the :variable:`userstat_running` variable.
23
24System Variables
25================
26
27.. variable:: userstat_running
28
29 :version 5.5.10-20.1: Renamed to :variable:`userstat`
30 :cli: Yes
31 :conf: Yes
32 :scope: Global
33 :dyn: Yes
34 :vartype: BOOLEAN
35 :default: OFF
36 :range: ON/OFF
37
38Enables or disables collection of statistics. The default is ``OFF``, meaning no statistics are gathered. This is to ensure that the statistics collection doesn't cause any extra load on the server unless desired.
39
40
41INFORMATION_SCHEMA Tables
42=========================
43
44.. table:: INFORMATION_SCHEMA.CLIENT_STATISTICS
45
46 :column CLIENT: The IP address or hostname from which the connection originated.
47 :column TOTAL_CONNECTIONS: The number of connections created for this client.
48 :column CONCURRENT_CONNECTIONS: The number of concurrent connections for this client.
49 :column CONNECTED_TIME: The cumulative number of seconds elapsed while there were connections from this client.
50 :column BUSY_TIME: The cumulative number of seconds there was activity on connections from this client.
51 :column CPU_TIME: The cumulative CPU time elapsed, in seconds, while servicing this client``s connections.
52 :column BYTES_RECEIVED: The number of bytes received from this client's connections.
53 :column BYTES_SENT: The number of bytes sent to this client's connections.
54 :column BINLOG_BYTES_WRITTEN: The number of bytes written to the binary log from this client's connections.
55 :column ROWS_FETCHED: The number of rows fetched by this client's connections.
56 :column ROWS_UPDATED: The number of rows updated by this client's connections.
57 :column TABLE_ROWS_READ: The number of rows read from tables by this client's connections. (It may be different from ``ROWS_FETCHED``.)
58 :column SELECT_COMMANDS: The number of ``SELECT`` commands executed from this client's connections.
59 :column UPDATE_COMMANDS: The number of ``UPDATE`` commands executed from this client's connections.
60 :column OTHER_COMMANDS: The number of other commands executed from this client's connections.
61 :column COMMIT_TRANSACTIONS: The number of ``COMMIT`` commands issued by this client's connections.
62 :column ROLLBACK_TRANSACTIONS: The number of ``ROLLBACK`` commands issued by this client's connections.
63 :column DENIED_CONNECTIONS: The number of connections denied to this client.
64 :column LOST_CONNECTIONS: The number of this client's connections that were terminated uncleanly.
65 :column ACCESS_DENIED: The number of times this client's connections issued commands that were denied.
66 :column EMPTY_QUERIES: The number of times this client's connections sent empty queries to the server.
67
68This table holds statistics about client connections. The Percona version of the feature restricts this table's visibility to users who have the ``SUPER`` or ``PROCESS`` privilege.
69
70Example: ::
71
72 mysql> SELECT * FROM INFORMATION_SCHEMA.CLIENT_STATISTICS\G
73 *************************** 1. row ***************************
74 CLIENT: 10.1.12.30
75 TOTAL_CONNECTIONS: 20
76 CONCURRENT_CONNECTIONS: 0
77 CONNECTED_TIME: 0
78 BUSY_TIME: 93
79 CPU_TIME: 48
80 BYTES_RECEIVED: 5031
81 BYTES_SENT: 276926
82 BINLOG_BYTES_WRITTEN: 217
83 ROWS_FETCHED: 81
84 ROWS_UPDATED: 0
85 TABLE_ROWS_READ: 52836023
86 SELECT_COMMANDS: 26
87 UPDATE_COMMANDS: 1
88 OTHER_COMMANDS: 145
89 COMMIT_TRANSACTIONS: 1
90 ROLLBACK_TRANSACTIONS: 0
91 DENIED_CONNECTIONS: 0
92 LOST_CONNECTIONS: 0
93 ACCESS_DENIED: 0
94 EMPTY_QUERIES: 0
95
96
97.. table:: INFORMATION_SCHEMA.INDEX_STATISTICS
98
99 :column TABLE_SCHEMA: The schema (database) name.
100 :column TABLE_NAME: The table name.
101 :column INDEX_NAME: The index name (as visible in ``SHOW CREATE TABLE``).
102 :column ROWS_READ: The number of rows read from this index.
103
104This table shows statistics on index usage. An older version of the feature contained a single column that had the ``TABLE_SCHEMA``, ``TABLE_NAME`` and ``INDEX_NAME`` columns concatenated together. The |Percona| version of the feature separates these into three columns. Users can see entries only for tables to which they have ``SELECT`` access.
105
106This table makes it possible to do many things that were difficult or impossible previously. For example, you can use it to find unused indexes and generate DROP commands to remove them.
107
108Example: ::
109
110 mysql> SELECT * FROM INFORMATION_SCHEMA.INDEX_STATISTICS
111 WHERE TABLE_NAME='tables_priv';
112 +--------------+-----------------------+--------------------+-----------+
113 | TABLE_SCHEMA | TABLE_NAME | INDEX_NAME | ROWS_READ |
114 +--------------+-----------------------+--------------------+-----------+
115 | mysql | tables_priv | PRIMARY | 2 |
116 +--------------+-----------------------+--------------------+-----------+
117
118
119
120.. table:: INFORMATION_SCHEMA.TABLE_STATISTICS
121
122 :column TABLE_SCHEMA: The schema (database) name.
123 :column TABLE_NAME: The table name.
124 :column ROWS_READ: The number of rows read from the table.
125 :column ROWS_CHANGED: The number of rows changed in the table.
126 :column ROWS_CHANGED_X_INDEXES: The number of rows changed in the table, multiplied by the number of indexes changed.
127
128This table is similar in function to the ``INDEX_STATISTICS`` table.
129
130Example: ::
131
132 mysql> SELECT * FROM INFORMATION_SCHEMA.TABLE_STATISTICS
133 WHERE TABLE_NAME=``tables_priv``;
134 +--------------+-------------------------------+-----------+--------------+------------------------+
135 | TABLE_SCHEMA | TABLE_NAME | ROWS_READ | ROWS_CHANGED | ROWS_CHANGED_X_INDEXES |
136 +--------------+-------------------------------+-----------+--------------+------------------------+
137 | mysql | tables_priv | 2 | 0 | 0 |
138 +--------------+-------------------------------+-----------+--------------+------------------------+
139
140
141.. table:: INFORMATION_SCHEMA.THREAD_STATISTICS
142
143 :column THREAD_ID: int(21)
144 :column TOTAL_CONNECTIONS: int(21)
145 :column CONCURRENT_CONNECTIONS: int(21)
146 :column CONNECTED_TIME: int(21)
147 :column BUSY_TIME: int(21)
148 :column CPU_TIME: int(21)
149 :column BYTES_RECEIVED: int(21)
150 :column BYTES_SENT: int(21)
151 :column BINLOG_BYTES_WRITTEN: int(21)
152 :column ROWS_FETCHED: int(21)
153 :column ROWS_UPDATED: int(21)
154 :column TABLE_ROWS_READ: int(21)
155 :column SELECT_COMMANDS: int(21)
156 :column UPDATE_COMMANDS: int(21)
157 :column OTHER_COMMANDS: int(21)
158 :column COMMIT_TRANSACTIONS: int(21)
159 :column ROLLBACK_TRANSACTIONS: int(21)
160 :column DENIED_CONNECTIONS: int(21)
161 :column LOST_CONNECTIONS: int(21)
162 :column ACCESS_DENIED: int(21)
163 :column EMPTY_QUERIES: int(21)
164
165.. table:: INFORMATION_SCHEMA.USER_STATISTICS
166
167 :column USER: The username. The value ``#mysql_system_user#`` appears when there is no username (such as for the slave SQL thread).
168 :column TOTAL_CONNECTIONS: The number of connections created for this user.
169 :column CONCURRENT_CONNECTIONS: The number of concurrent connections for this user.
170 :column CONNECTED_TIME: The cumulative number of seconds elapsed while there were connections from this user.
171 :column BUSY_TIME: The cumulative number of seconds there was activity on connections from this user.
172 :column CPU_TIME: The cumulative CPU time elapsed, in seconds, while servicing this user's connections.
173 :column BYTES_RECEIVED: The number of bytes received from this user's connections.
174 :column BYTES_SENT: The number of bytes sent to this user's connections.
175 :column BINLOG_BYTES_WRITTEN: The number of bytes written to the binary log from this user's connections.
176 :column ROWS_FETCHED: The number of rows fetched by this user's connections.
177 :column ROWS_UPDATED: The number of rows updated by this user's connections.
178 :column TABLE_ROWS_READ: The number of rows read from tables by this user's connections. (It may be different from ``ROWS_FETCHED``.)
179 :column SELECT_COMMANDS: The number of ``SELECT`` commands executed from this user's connections.
180 :column UPDATE_COMMANDS: The number of ``UPDATE`` commands executed from this user's connections.
181 :column OTHER_COMMANDS: The number of other commands executed from this user's connections.
182 :column COMMIT_TRANSACTIONS: The number of ``COMMIT`` commands issued by this user's connections.
183 :column ROLLBACK_TRANSACTIONS: The number of ``ROLLBACK`` commands issued by this user's connections.
184 :column DENIED_CONNECTIONS: The number of connections denied to this user.
185 :column LOST_CONNECTIONS: The number of this user's connections that were terminated uncleanly.
186 :column ACCESS_DENIED: The number of times this user's connections issued commands that were denied.
187 :column EMPTY_QUERIES: The number of times this user's connections sent empty queries to the server.
188
189This table contains information about user activity. The |Percona| version of the patch restricts this table's visibility to users who have the ``SUPER`` or ``PROCESS`` privilege.
190
191The table gives answers to questions such as which users cause the most load, and whether any users are being abusive. It also lets you measure how close to capacity the server may be. For example, you can use it to find out whether replication is likely to start falling behind.
192
193Example: ::
194
195 mysql> SELECT * FROM INFORMATION_SCHEMA.USER_STATISTICS\G
196 *************************** 1. row ***************************
197 USER: root
198 TOTAL_CONNECTIONS: 5592
199 CONCURRENT_CONNECTIONS: 0
200 CONNECTED_TIME: 6844
201 BUSY_TIME: 179
202 CPU_TIME: 72
203 BYTES_RECEIVED: 603344
204 BYTES_SENT: 15663832
205 BINLOG_BYTES_WRITTEN: 217
206 ROWS_FETCHED: 9793
207 ROWS_UPDATED: 0
208 TABLE_ROWS_READ: 52836023
209 SELECT_COMMANDS: 9701
210 UPDATE_COMMANDS: 1
211 OTHER_COMMANDS: 2614
212 COMMIT_TRANSACTIONS: 1
213 ROLLBACK_TRANSACTIONS: 0
214 DENIED_CONNECTIONS: 0
215 LOST_CONNECTIONS: 0
216 ACCESS_DENIED: 0
217 EMPTY_QUERIES: 0
218
219Commands Provided
220=================
221
222 * ``FLUSH CLIENT_STATISTICS``
223
224 * ``FLUSH INDEX_STATISTICS``
225
226 * ``FLUSH TABLE_STATISTICS``
227
228 * ``FLUSH THREAD_STATISTICS``
229
230 * ``FLUSH USER_STATISTICS``
231
232These commands discard the specified type of stored statistical information.
233
234 * ``SHOW CLIENT_STATISTICS``
235 * ``SHOW INDEX_STATISTICS``
236 * ``SHOW TABLE_STATISTICS``
237 * ``SHOW THREAD_STATISTICS``
238 * ``SHOW USER_STATISTICS``
239
240These commands are another way to display the information you can get from the ``INFORMATION_SCHEMA`` tables. The commands accept ``WHERE`` clauses. They also accept but ignore ``LIKE`` clauses.
241
242
0243
=== added file 'doc/source/flexibility/mysqldump_ignore_create_error.rst'
--- doc/source/flexibility/mysqldump_ignore_create_error.rst 1970-01-01 00:00:00 +0000
+++ doc/source/flexibility/mysqldump_ignore_create_error.rst 2013-05-22 08:54:39 +0000
@@ -0,0 +1,22 @@
1.. _mysqldump_ignore_create_error:
2
3======================================
4 Ignoring missing tables in mysqldump
5======================================
6
7In case table name was changed during the :command:`mysqldump` process taking place, :command:`mysqldump` would stop with error: ::
8
9 Couldn't execute 'show create table testtable'
10 Table 'testdb.tabletest' doesn't exist (1146)\n")
11
12This could happen if :command:`mysqldump` was taking a backup of a working slave and during that process table name would get changed. This error happens because :command:`mysqldump` takes the list of the tables at the beginning of the dump process but the ``SHOW CREATE TABLE`` happens just before the table is being dumped.
13
14With this option :command:`mysqldump` will still show error to ``stderr``, but it will continue to work and dump the rest of the tables.
15
16Version Specific Information
17============================
18
19 * :rn:`5.6.5-60.0`
20 :command:`mysqldump` option :option:`--ignore-create-error` introduced
21
22
023
=== removed directory 'doc/source/reliability'
=== removed file 'doc/source/reliability/error_pad.rst'
--- doc/source/reliability/error_pad.rst 2013-05-22 08:54:33 +0000
+++ doc/source/reliability/error_pad.rst 1970-01-01 00:00:00 +0000
@@ -1,55 +0,0 @@
1.. _error_pad:
2
3==========================
4 Error Code Compatibility
5==========================
6
7|Percona Server| with |XtraDB| has error code incompatibilities with |MySQL| 5.5. It is important to maintain compatibility in the error codes used by the servers. For example, scripts that may be run on both servers could contain references to error codes.
8
9The reasons for the current incompatibilities are:
10
11 * |Percona Server| with |XtraDB| contains features that have been backported from MyQL 5.5. Some of the |MySQL| 5.5 features added new error codes.
12
13 * Some |Percona Server| with |XtraDB| features have added new error codes.
14
15The solution to the first problem is to preserve |MySQL| 5.5 error codes in the |Percona Server|. An example of where this has been done is |Percona Server| feature Query Cache Enhancements. This feature adds error ``ER_QUERY_CACHE_DISABLED`` to the |Percona Server|, which is defined as error code 1651 in |MySQL| 5.5.
16
17After migrating |Percona Server| / |XtraDB| to |MySQL| 5.5, users might experience troubles because of this.
18
19The solution to the second problem is to insure that unique error codes are chosen, when adding new ones to |Percona Server|, that will never be duplicated during |MySQL| development.
20
21For example, |MySQL| has a tool ``comp_err`` that generates:
22
23 - :file:`errmsg.sys` files
24
25 - header file :file:`include/mysqld_error.h`
26
27 - header file :file:`include/mysqld_ername.h`
28
29from the file :file:`errmsg.txt`.
30
31To keep error numbers consistent, we should add some fictive errors to :file:`errmsg.txt`, because ``comp_err`` assigns error code numbers sequentially, without gaps.
32
33I propose patch to ``comp_err``.
34
35This patch allows usage of a new syntax, with prefix ``PADD``, for example: ::
36
37 PADD_QUERY_CACHE_DISABLED 1651
38 eng "ER_QUERY_CACHE_DISABLED padding to 1651 error"
39 ER_QUERY_CACHE_DISABLED
40 eng "Query cache is disabled; restart the server with query_cache_type=1 to enable it"
41
42comp_err with my patch padds empty intervals (from last error code number to 1651) by error message ``ER_QUERY_CACHE_DISABLED padding to 1651 error``, i.e. and ``ER_QUERY_CACHE_DISABLED`` now has error code 1651 (as desired). I propose to use this patch for Percona errors, for example: ::
43
44 PADD_PERCONA_NEW_ERROR_CODE 4000
45 end "Padd empty space to error code number 4000 (Percona error codes)"
46 ...some percona error codes...
47
48Patch only adds prefix ``PADD_`` and padds error in sys files. All other |MySQL| code (load*.sys files, my_error, etc) works as old one.
49
50
51Version-Specific Information
52============================
53
54 * 5.5.8-20.0
55 Full functionality available.
560
=== removed file 'doc/source/reliability/innodb_corrupt_table_action.rst'
--- doc/source/reliability/innodb_corrupt_table_action.rst 2013-04-10 14:43:41 +0000
+++ doc/source/reliability/innodb_corrupt_table_action.rst 1970-01-01 00:00:00 +0000
@@ -1,35 +0,0 @@
1.. _innodb_corrupt_table_action_page:
2
3=========================
4 Handle Corrupted Tables
5=========================
6
7Instead of crashing the server as they used to do, corrupted |InnoDB| tables are simply disabled, so that the database remains available while the corruption is being fixed.
8
9This feature adds a new system variable.
10
11Version Specific Information
12============================
13
14 * 5.6.10-60.2:
15 Feature ported from |Percona Server| 5.5
16
17System Variables
18================
19
20.. variable:: innodb_corrupt_table_action
21
22 :version 5.6.10-60.2: Introduced.
23 :cli: Yes
24 :conf: Yes
25 :scope: Global
26 :dyn: Yes
27 :vartype: ULONG
28 :range: ``assert``, ``warn``, ``salvage``
29
30* With the default value |XtraDB| will intentionally crash the server with an assertion failure as it would normally do when detecting corrupted data in a single-table tablespace.
31
32* If the ``warn`` value is used it will pass corruption of the table as ``corrupt table`` instead of crashing itself. For this to work :option:`innodb_file_per_table` should be enabled. All file I/O for the datafile after detected as corrupt is disabled, except for the deletion.
33
34* When the option value is ``salvage``, |XtraDB| allows read access to a corrupted tablespace, but ignores corrupted pages".
35
360
=== removed file 'doc/source/reliability/log_connection_error.rst'
--- doc/source/reliability/log_connection_error.rst 2013-05-22 08:54:33 +0000
+++ doc/source/reliability/log_connection_error.rst 1970-01-01 00:00:00 +0000
@@ -1,14 +0,0 @@
1.. _log_connection_error:
2
3==============================
4 Too Many Connections Warning
5==============================
6
7
8This feature issues the warning ``Too many connections`` to the log, if ``log_warnings`` is enabled.
9
10Version-Specific Information
11============================
12
13 * 5.5.8-20.0:
14 Full functionality available.
150
=== removed file 'doc/source/reliability/show_slave_status_nolock.rst'
--- doc/source/reliability/show_slave_status_nolock.rst 2013-05-22 08:54:33 +0000
+++ doc/source/reliability/show_slave_status_nolock.rst 1970-01-01 00:00:00 +0000
@@ -1,23 +0,0 @@
1.. _show_slave_status_nolock:
2
3=================================
4 Lock-Free ``SHOW SLAVE STATUS``
5=================================
6
7The ``STOP SLAVE`` and ``SHOW SLAVE STATUS`` commands can conflict due to a global lock in the situation where one thread on a slave attempts to execute a ``STOP SLAVE`` command, while a second thread on the slave is already running a command that takes a long time to execute.
8
9If a ``STOP SLAVE`` command is given in this situation, it will wait and not complete execution until the long-executing thread has completed its task. If another thread now executes a ``SHOW SLAVE STATUS`` command while the STOP SLAVE command is waiting to complete, the ``SHOW SLAVE STATUS`` command will not be able to execute while the ``STOP SLAVE`` command is waiting.
10
11This features modifies the ``SLOW SLAVE STATUS`` syntax to allow: ::
12
13 SLOW SLAVE STATUS NOLOCK
14
15This will display the slave's status as if there were no lock, allowing the user to detect and understand the situation that is occurring.
16
17**NOTE:** The information given when ``NOLOCK`` is used may be slightly inconsistent with the actual situation while the lock is being held.
18
19
20Version Specific Information
21============================
22
23 * 5.5.8-20.0:
240
=== removed file 'doc/source/upstream-bug-fixes.rst'
--- doc/source/upstream-bug-fixes.rst 2013-05-22 08:54:33 +0000
+++ doc/source/upstream-bug-fixes.rst 1970-01-01 00:00:00 +0000
@@ -1,133 +0,0 @@
1.. _upstream_bug_fixes:
2
3=============================================================
4 List of upstream |MySQL| bugs fixed in |Percona Server| 5.6
5=============================================================
6
7+-------------------------------------------------------------------------------------------------------------+
8|:Upstream bug: :mysqlbug:`67504` - Duplicate error in replication with slave triggers and auto increment |
9|:Launchpad bug: :bug:`1068210` |
10|:Upstream state: Verified (checked on 2013-02-21) |
11|:Fix Released: :rn:`5.6.11-60.3` |
12|:Upstream fix: N/A |
13+-------------------------------------------------------------------------------------------------------------+
14|:Upstream bug: :mysqlbug:`67974` - Server crashes in add_identifier on concurrent ALTER TABLE and SHOW ENGINE|
15|:Launchpad bug: :bug:`1017192` |
16|:Upstream state: N/A |
17|:Fix Released: :rn:`5.6.11-60.3` |
18|:Upstream fix: N/A |
19+-------------------------------------------------------------------------------------------------------------+
20|:Upstream bug: :mysqlbug:`68045` - security vulnerability CVE-2012-4414 |
21|:Launchpad bug: :bug:`1049871` |
22|:Upstream state: N/A |
23|:Fix Released: :rn:`5.6.11-60.3` |
24|:Upstream fix: N/A |
25+-------------------------------------------------------------------------------------------------------------+
26|:Upstream bug: :mysqlbug:`66550` - security vulnerability CVE-2012-4414 |
27|:Launchpad bug: :bug:`1049871` |
28|:Upstream state: N/A |
29|:Fix Released: :rn:`5.6.11-60.3` |
30|:Upstream fix: N/A |
31+-------------------------------------------------------------------------------------------------------------+
32|:Upstream bug: :mysqlbug:`67685` - security vulnerability CVE-2012-5611 |
33|:Launchpad bug: :bug:`1083377` |
34|:Upstream state: N/A |
35|:Fix Released: :rn:`5.6.11-60.3` |
36|:Upstream fix: N/A |
37+-------------------------------------------------------------------------------------------------------------+
38|:Upstream bug: :mysqlbug:`66237` - Temporary files created by binary log cache are not purged after transa...|
39|:Launchpad bug: :bug:`1070856` |
40|:Upstream state: Verified (checked on 2013-02-21) |
41|:Fix Released: :rn:`5.6.11-60.3` |
42|:Upstream fix: N/A |
43+-------------------------------------------------------------------------------------------------------------+
44|:Upstream bug: :mysqlbug:`67606` - MySQL crashes with segmentation fault when disk quota is reached |
45|:Launchpad bug: :bug:`1079596` |
46|:Upstream state: Duplicate |
47|:Fix Released: :rn:`5.6.11-60.3` |
48|:Upstream fix: N/A |
49+-------------------------------------------------------------------------------------------------------------+
50|:Upstream bug: :mysqlbug:`62856` - Check for "stack overrun" doesn't work with gcc-4.6, server crashes |
51|:Launchpad bug: :bug:`1042517` |
52|:Upstream state: Verified (checked on 2013-02-21) |
53|:Fix Released: :rn:`5.6.11-60.3` |
54|:Upstream fix: N/A |
55+-------------------------------------------------------------------------------------------------------------+
56|:Upstream bug: :mysqlbug:`61180` - korr/store macros in my_global.h assume the argument to be a char pointer |
57|:Launchpad bug: :bug:`1042517` |
58|:Upstream state: Verified (checked on 2013-02-21) |
59|:Fix Released: :rn:`5.6.11-60.3` |
60|:Upstream fix: N/A |
61+-------------------------------------------------------------------------------------------------------------+
62|:Upstream bug: :mysqlbug:`61179` - Unoptimized versions of korr/store macros in my_global.h are used on ... |
63|:Launchpad bug: :bug:`1042517` |
64|:Upstream state: Verified (checked on 2013-02-21) |
65|:Fix Released: :rn:`5.6.11-60.3` |
66|:Upstream fix: N/A |
67+-------------------------------------------------------------------------------------------------------------+
68|:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|
69|:Launchpad bug: :bug:`1042517` |
70|:Upstream state: Verified (checked on 2013-02-21) |
71|:Fix Released: :rn:`5.6.11-60.3` |
72|:Upstream fix: N/A |
73+-------------------------------------------------------------------------------------------------------------+
74|:Upstream bug: :mysqlbug:`54127` - mysqld segfaults when built using --with-max-indexes=128 |
75|:Launchpad bug: :bug:`1042517` |
76|:Upstream state: Verified (checked on 2013-02-21) |
77|:Fix Released: :rn:`5.5.10-60.3` |
78|:Upstream fix: N/A |
79+-------------------------------------------------------------------------------------------------------------+
80|:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no. |
81|:Launchpad bug: :bug:`1013432` |
82|:Upstream state: Verified (checked on 2013-02-21) |
83|:Fix Released: :rn:`5.6.11-60.3` |
84|:Upstream fix: N/A |
85+-------------------------------------------------------------------------------------------------------------+
86|:Upstream bug: :mysqlbug:`66301` - INSERT ... ON DUPLICATE KEY UPDATE + innodb_autoinc_lock_mode=1 is broken |
87|:Launchpad bug: :bug:`1035225` |
88|:Upstream state: Verified (checked on 2013-02-21) |
89|:Fix Released: :rn:`5.6.11-60.3` |
90|:Upstream fix: N/A |
91+-------------------------------------------------------------------------------------------------------------+
92|:Upstream bug: :mysqlbug:`60743` - typo in cmake/dtrace.cmake |
93|:Launchpad bug: :bug:`1013455` |
94|:Upstream state: Verified (checked on 2013-02-21) |
95|:Fix Released: :rn:`5.6.11-60.3` |
96|:Upstream fix: N/A |
97+-------------------------------------------------------------------------------------------------------------+
98|:Upstream bug: :mysqlbug:`64663` - Segfault when adding indexes to InnoDB temporary tables |
99|:Launchpad bug: :bug:`999147` |
100|:Upstream state: Verified (checked on 2013-02-21) |
101|:Fix Released: :rn:`5.6.11-60.3` |
102|:Upstream fix: N/A |
103+-------------------------------------------------------------------------------------------------------------+
104|:Upstream bug: :mysqlbug:`64432` - Bug :mysqlbug:`54330` (Broken fast index creation) was never fixed in 5.5 |
105|:Launchpad bug: :bug:`939485` |
106|:Upstream state: Documenting (checked on 2013-02-21) |
107|:Fix Released: :rn:`5.6.11-60.3` |
108|:Upstream fix: N/A |
109+-------------------------------------------------------------------------------------------------------------+
110|:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |
111|:Launchpad bug: :bug:`800035` |
112|:Upstream state: Verified (checked on 2013-02-21) |
113|:Fix Released: :rn:`5.6.11-60.3` |
114|:Upstream fix: N/A |
115+-------------------------------------------------------------------------------------------------------------+
116|:Upstream bug: :mysqlbug:`60788` - InnoDB crashes with an assertion failure when receiving a signal on pwrite|
117|:Launchpad bug: :bug:`764395` |
118|:Upstream state: Duplicate |
119|:Fix Released: :rn:`5.6.11-60.3` |
120|:Upstream fix: N/A |
121+-------------------------------------------------------------------------------------------------------------+
122|:Upstream bug: :mysqlbug:`68116` - InnoDB monitor may hit an assertion error in buf_page_get_gen in debug ...|
123|:Launchpad bug: :bug:`1100178` |
124|:Upstream state: Analyzing (checked on 2013-02-21) |
125|:Fix Released: :rn:`5.6.10-60.2` |
126|:Upstream fix: N/A |
127+-------------------------------------------------------------------------------------------------------------+
128|:Upstream bug: :mysqlbug:`65946` - Sid_map::Sid_map calls DBUG which may have unitialized THR_KEY_mysys and..|
129|:Launchpad bug: :bug:`1050758` |
130|:Upstream state: Duplicate |
131|:Fix Released: :rn:`5.6.5-60.0` |
132|:Upstream fix: N/A |
133+-------------------------------------------------------------------------------------------------------------+

Subscribers

People subscribed via source and target branches