Merge lp:~hrvojem/percona-server/doc-28 into lp:percona-server/5.6

Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Laurynas Biveinis
Approved revision: 367
Merged at revision: 375
Proposed branch: lp:~hrvojem/percona-server/doc-28
Merge into: lp:percona-server/5.6
Diff against target: 2374 lines (+751/-859)
35 files modified
doc/source/changed_in_56.rst (+4/-4)
doc/source/conf.py (+3/-1)
doc/source/diagnostics/innodb_deadlock_count.rst (+1/-1)
doc/source/diagnostics/innodb_show_status.rst (+135/-164)
doc/source/diagnostics/misc_info_schema_tables.rst (+40/-0)
doc/source/diagnostics/mysql_syslog.rst (+2/-2)
doc/source/diagnostics/show_engines.rst (+1/-7)
doc/source/diagnostics/slow_extended.rst (+355/-0)
doc/source/diagnostics/slow_extended_55.rst (+0/-377)
doc/source/diagnostics/thread_based_profiling.rst (+2/-2)
doc/source/diagnostics/user_stats.rst (+5/-5)
doc/source/flexibility/buff_read_ahead_area.rst (+0/-36)
doc/source/flexibility/innodb_files_extend.rst (+0/-25)
doc/source/flexibility/log_warnings_suppress.rst (+3/-11)
doc/source/flexibility/max_binlog_files.rst (+2/-2)
doc/source/index.rst (+18/-4)
doc/source/index_info_schema_tables.rst (+8/-36)
doc/source/installation.rst (+1/-1)
doc/source/management/changed_page_tracking.rst (+4/-5)
doc/source/management/enforce_engine.rst (+1/-1)
doc/source/management/expanded_program_option_modifiers.rst (+1/-1)
doc/source/management/innodb_fake_changes.rst (+12/-2)
doc/source/management/innodb_fast_index_creation.rst (+0/-63)
doc/source/management/innodb_kill_idle_trx.rst (+1/-1)
doc/source/management/pam_plugin.rst (+1/-1)
doc/source/management/secure_file_priv_extended.rst (+1/-1)
doc/source/management/udf_maatkit.rst (+0/-49)
doc/source/management/udf_percona_toolkit.rst (+54/-0)
doc/source/management/utility_user.rst (+4/-4)
doc/source/performance/innodb_numa_support.rst (+1/-1)
doc/source/performance/query_cache_enhance.rst (+8/-42)
doc/source/reliability/error_pad.rst (+6/-6)
doc/source/reliability/log_connection_error.rst (+2/-2)
doc/source/reliability/show_slave_status_nolock.rst (+4/-2)
doc/source/scalability/innodb_io.rst (+71/-0)
To merge this branch: bzr merge lp:~hrvojem/percona-server/doc-28
Reviewer Review Type Date Requested Status
Laurynas Biveinis (community) Approve
Review via email: mp+166285@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

- Please rebase on the latest trunk that has the file-id fixes. They have touched docs as well.

- Please also use https://code.launchpad.net/~laurynas-biveinis/percona-server/5.6-merge-4 as a prerequisite branch. It merges more 5.5 revisions, including doc ones.

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

    - the list of status variables itself does not look updated?
      i.e. AFAIK it should not have 1 or 10 second loops one but
      should have some new ones like background or active loops.
    - innodb_show_status.rst: just "feature ported ... ", no need for
      the other changes under version-specific change list.
    - doc/source/diagnostics/innodb_stats.rst - I think it's
      redundant, it should be fully replaced by the upstream
      features, so it needs upgrade documentation.
      - innodb_stats_method is an upstream feature.
      - other variables do not exist.
      - INNODB_SYS_TABLES, INNODB_SYS_TABLESTATS, INNODB_SYS_INDEXES,
        INNODB_SYS_COLUMNS, INNODB_SYS_FIELDS, INNODB_SYS_FOREIGN,
        INNODB_SYS_FOREIGN_COLS, INNODB_TABLE_STATS,
        INNODB_INDEX_STATS are upstream tables. Their schemas are
        different too IIRC.
    - doc/source/diagnostics/slow_extended.rst:
      - Maciej is no longer with Percona
      - No need to document upstream variables
        log_slow_admin_statements and log_slow_slave_statements
      - The log entry example is outdated, i.e. rows_read: is not
        there anymore, needs updating to the actual current output.
      - The profiling one too.
    - doc/source/diagnostics/user_stats.rst:
      - 5.6.11 changes: "Feature ported from PS 5.5"
    - doc/source/index_info_schema_tables.rst:
      - XTRADB_INTERNAL_HASH_TABLES, XTRADB_READ_VIEW, XTRADB_RSEG
        tables do not exist?
    - doc/source/installation.rst:
      ":ref:`pam_plugin` is not built with the server by
      default. ... "
    - doc/source/management/innodb_fast_index_creation.rst has been
      ported to 5.6.
    - doc/source/management/pam_plugin.rst: "integrated with |Percona
      Server|."

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

    - Line 59: bug 29123/29126 conflict, probably in the lower
      versions as well.
    - Line 102: should be fixed in lower versions as well?
    - Line 702: can be removed (also from 5.5 too I guess).
    - doc/source/diagnostics/thread_based_profiling.rst has been
      ported to 5.6.
    - Where are innodb_log_block_size docs?

Should I report the lower version issues separately?

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

    - innodb_io.rst: innodb_flush_method=ALL_O_DIRECT (dropped),
      innodb_log_file_size (replaced in upstream) have not been
      ported. innodb_purge_threads default has not been ported
      (replaced in upstream). That leaves ported status vars,
      innodb_log_block_size, and
      innodb_use_global_flush_log_at_trx_commit. The introduction
      needs updating, it doesn't seem to have received any since 5.0,
      i.e. "Note that some of these parameters are already available
      in the |InnoDB| plugin." should be removed, the rest rewritten
      perhaps.

review: Needs Fixing
lp:~hrvojem/percona-server/doc-28 updated
367. By Hrvoje Matijakovic on 2013-06-03

- PS-5.6 doc cleanup and update - DOC-28
- updated index of I_S tables introduced in PS-5.6 - DOC-11

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) :
review: Approve
Revision history for this message
Stewart Smith (stewart) wrote :

Hrvoje Matijakovic <email address hidden> writes:
> - * 5.5.8-20.0:
> + * :rn:`5.6.11-60.3`:

I wonder if we should keep the 5.5 introduction number in the 5.6 docs
too (perhaps as well as the 5.6 introduction version).

--
Stewart Smith

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

Stewart -

What would be the advantage? The 5.5 docs are there too. I'd prefer to have only 5.6 versions in 5.6, I think I already asked Hrvoje to remove the 5.5 versions earlier

Revision history for this message
Stewart Smith (stewart) wrote :

Laurynas Biveinis <email address hidden> writes:
> What would be the advantage? The 5.5 docs are there too. I'd prefer to
> have only 5.6 versions in 5.6, I think I already asked Hrvoje to
> remove the 5.5 versions earlier

I guess it's fine either way....

--
Stewart Smith

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/source/changed_in_56.rst'
2--- doc/source/changed_in_56.rst 2013-05-10 13:29:38 +0000
3+++ doc/source/changed_in_56.rst 2013-06-03 10:03:31 +0000
4@@ -10,15 +10,15 @@
5
6 * `fast_index_creation <http://www.percona.com/doc/percona-server/5.5/management/innodb_fast_index_creation.html>`_ (use MySQL 5.6's ALGORITHM= option instead)
7 * `HandlerSocket <http://www.percona.com/doc/percona-server/5.5/performance/handlersocket.html>`_ (may return when HandlerSocket supports MySQL 5.6)
8- * SHOW [GLOBAL] TEMPORARY TABLES functionality is now only available via the INFORMATION_SCHEMA tables TEMPORARY_TABLES and GLOBAL_TEMPORARY_TABLES.
9+ * SHOW [GLOBAL] TEMPORARY TABLES functionality is now only available via the INFORMATION_SCHEMA tables :table:`TEMPORARY_TABLES` and :table:`GLOBAL_TEMPORARY_TABLES`.
10 * `InnoDB timer-based Concurrency Throttling <http://www.percona.com/doc/percona-server/5.5/performance/innodb_thread_concurrency_timer_based.html>`_
11 * `InnoDB Recovery Stats <http://www.percona.com/doc/percona-server/5.5/management/innodb_recovery_patches.html>`_
12
13 Some features that were present in |Percona Server| 5.5 have been replaced by a different implementation of the same/similar functionality in |Percona Server| 5.6. These are:
14
15- * SHOW INNODB STATUS section "OLDEST VIEW" has been replaced by the XTRADB_READ_VIEW INFORMATION_SCHEMA table.
16- * SHOW INNODB STATUS sections on memory usage for InnoDB/XtraDB hash tables has been replaced by the XTRADB_INTERNAL_HASH_TABLES INFORMATION_SCHEMA table.
17- * The INNODB_RSEG table has been renamed to XTRADB_RSEG
18+ * ``SHOW ENGINE INNODB STATUS`` section "OLDEST VIEW" has been replaced by the :table:`XTRADB_READ_VIEW` INFORMATION_SCHEMA table.
19+ * ``SHOW ENGINE INNODB STATUS`` sections on memory usage for InnoDB/XtraDB hash tables has been replaced by the :table:`XTRADB_INTERNAL_HASH_TABLES` INFORMATION_SCHEMA table.
20+ * The :table:`INNODB_RSEG` table has been renamed to :table:`XTRADB_RSEG`.
21
22 Some |Percona Server| 5.5 features have been replaced by similar or equivalent MySQL 5.6 features, so we now keep the MySQL 5.6 implementations in |Percona Server| 5.6. These are:
23
24
25=== modified file 'doc/source/conf.py'
26--- doc/source/conf.py 2013-05-27 03:01:29 +0000
27+++ doc/source/conf.py 2013-06-03 10:03:31 +0000
28@@ -108,6 +108,8 @@
29
30 .. |XtraBackup| replace:: *XtraBackup*
31
32+.. |Percona XtraBackup| replace:: *Percona XtraBackup*
33+
34 .. |Percona Server| replace:: *Percona Server*
35
36 .. |Percona| replace:: *Percona*
37@@ -265,6 +267,6 @@
38 intersphinx_mapping = {
39 'ps51' : ('http://www.percona.com/doc/percona-server/5.1/', None),
40 'ps55' : ('http://www.percona.com/doc/percona-server/5.5/', None),
41- 'xtrabackup' : ('http://www.percona.com/doc/percona-xtrabackup', None),
42+ 'xtrabackup' : ('http://www.percona.com/doc/percona-xtrabackup/2.1/', None),
43 'ptoolkit' : ('http://www.percona.com/doc/percona-toolkit/2.1/', None)
44 }
45
46=== modified file 'doc/source/diagnostics/innodb_deadlock_count.rst'
47--- doc/source/diagnostics/innodb_deadlock_count.rst 2013-05-27 13:59:13 +0000
48+++ doc/source/diagnostics/innodb_deadlock_count.rst 2013-06-03 10:03:31 +0000
49@@ -36,7 +36,7 @@
50 Version Specific Information
51 ============================
52
53- * 5.5.8-20.0:
54+ * :rn:`5.6.11-60.3`:
55 Full functionality available.
56
57 Status Variables
58
59=== modified file 'doc/source/diagnostics/innodb_show_status.rst'
60--- doc/source/diagnostics/innodb_show_status.rst 2013-05-10 09:39:17 +0000
61+++ doc/source/diagnostics/innodb_show_status.rst 2013-06-03 10:03:31 +0000
62@@ -1,16 +1,16 @@
63 .. _innodb_show_status:
64
65-======================
66- Show |InnoDB| Status
67-======================
68-
69-This 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.
70-
71-This feature modified the ``SHOW INNODB STATUS`` command as follows:
72+======================================
73+ Extended Show Engine |InnoDB| Status
74+======================================
75+
76+This feature reorganizes the output of ``SHOW ENGINE 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.
77+
78+This feature modified the ``SHOW ENGINE INNODB STATUS`` command as follows:
79
80 * ``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.
81
82- * Added two variables to control ``SHOW INNODB STATUS`` information presented (bugfix for `#29123 <http://bugs.mysql.com/bug.php?id=29126>`_):
83+ * Added two variables to control ``SHOW ENGINE INNODB STATUS`` information presented (bugfix for `#29123 <http://bugs.mysql.com/bug.php?id=29123>`_):
84
85 * :variable:`innodb_show_verbose_locks` - Whether to show records locked
86
87@@ -18,19 +18,15 @@
88
89 * 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.
90
91- * Added additional LOG section information (beginning in release 5.5.8-20.0).
92+ * Added additional LOG section information.
93
94 Version Specific Information
95 ============================
96
97- * 5.5.8-20.0
98- Added status variables showing information from ``SHOW INNODB STATUS``.
99-
100- * 5.5.8-20.0
101- Added additional information in the LOG section.
102-
103- * 5.5.10-20.1:
104- Renamed status variable :variable:`innodb_row_lock_numbers` to :variable:`innodb_current_row_locks`.
105+ * :rn:`5.6.11-60.3`:
106+
107+ Feature ported from |Percona Server| 5.5.
108+
109
110 Other Information
111 =================
112@@ -52,7 +48,7 @@
113 :default: 0
114 :range: 0 - 1
115
116-Specifies 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.
117+Specifies to show records locked in ``SHOW ENGINE 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.
118
119 .. variable:: innodb_show_locks_held
120
121@@ -64,62 +60,44 @@
122 :default: 10
123 :range: 0 - 1000
124
125-Specifies the number of locks held to print for each |InnoDB| transaction in SHOW INNODB STATUS.
126+Specifies the number of locks held to print for each |InnoDB| transaction in ``SHOW ENGINE INNODB STATUS``.
127
128
129 Status Variables
130 ================
131
132-The 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.
133+The status variables here contain information available in the output of ``SHOW ENGINE INNODB STATUS``, organized by the sections ``SHOW ENGINE INNODB STATUS`` displays. If you are familiar with the output of ``SHOW ENGINE INNODB STATUS``, you will probably already recognize the information these variables contain.
134
135
136 BACKGROUND THREAD
137 -----------------
138
139-The following variables contain information in the BACKGROUND THREAD section of the output from ``SHOW INNODB STATUS``. An example of that output is:
140-
141- Insert an example of BACKGROUND THREAD section output here.
142-
143-.. variable:: innodb_master_thread_1_second_loops
144-
145- :version 5.5.8-20.0: Introduced.
146- :vartype: Numeric
147- :scope: Global
148-
149-.. variable:: innodb_master_thread_10_second_loops
150-
151- :version 5.5.8-20.0: Introduced.
152- :vartype: Numeric
153- :scope: Global
154-
155-.. variable:: innodb_master_thread_background_loops
156-
157- :version 5.5.8-20.0: Introduced.
158- :vartype: Numeric
159- :scope: Global
160-
161-.. variable:: innodb_master_thread_main_flush_loops
162-
163- :version 5.5.8-20.0: Introduced.
164- :vartype: Numeric
165- :scope: Global
166-
167-.. variable:: innodb_master_thread_sleeps
168-
169- :version 5.5.8-20.0: Introduced.
170- :vartype: Numeric
171- :scope: Global
172-
173-.. variable:: innodb_background_log_sync
174-
175- :version 5.5.8-20.0: Introduced.
176- :vartype: Numeric
177- :scope: Global
178+The following variables contain information in the BACKGROUND THREAD section of the output from ``SHOW ENGINE INNODB STATUS``. An example of that output is: ::
179+
180+ -----------------
181+ BACKGROUND THREAD
182+ -----------------
183+ srv_master_thread loops: 1 srv_active, 0 srv_shutdown, 11844 srv_idle
184+ srv_master_thread log flush and writes: 11844
185+
186+
187+.. variable:: innodb_master_thread_active_loops
188+
189+ :version 5.6.11-60.3: Introduced.
190+ :vartype: Numeric
191+ :scope: Global
192+
193+.. variable:: innodb_master_thread_idle_loops
194+
195+ :version 5.6.11-60.3: Introduced.
196+ :vartype: Numeric
197+ :scope: Global
198+
199
200 SEMAPHORES
201 ----------
202
203-The following variables contain information in the SEMAPHORES section of the output from ``SHOW INNODB STATUS``. An example of that output is: ::
204+The following variables contain information in the SEMAPHORES section of the output from ``SHOW ENGINE INNODB STATUS``. An example of that output is: ::
205
206 ----------
207 SEMAPHORES
208@@ -131,281 +109,255 @@
209
210 .. variable:: innodb_mutex_os_waits
211
212- :version 5.5.8-20.0: Introduced.
213+ :version 5.6.11-60.3: Introduced.
214 :vartype: Numeric
215 :scope: Global
216
217 .. variable:: innodb_mutex_spin_rounds
218
219- :version 5.5.8-20.0: Introduced.
220+ :version 5.6.11-60.3: Introduced.
221 :vartype: Numeric
222 :scope: Global
223
224 .. variable:: innodb_mutex_spin_waits
225
226- :version 5.5.8-20.0: Introduced.
227+ :version 5.6.11-60.3: Introduced.
228 :vartype: Numeric
229 :scope: Global
230
231 .. variable:: innodb_s_lock_os_waits
232
233- :version 5.5.8-20.0: Introduced.
234+ :version 5.6.11-60.3: Introduced.
235 :vartype: Numeric
236 :scope: Global
237
238 .. variable:: innodb_s_lock_spin_rounds
239
240- :version 5.5.8-20.0: Introduced.
241+ :version 5.6.11-60.3: Introduced.
242 :vartype: Numeric
243 :scope: Global
244
245 .. variable:: innodb_s_lock_spin_waits
246
247- :version 5.5.8-20.0: Introduced.
248+ :version 5.6.11-60.3: Introduced.
249 :vartype: Numeric
250 :scope: Global
251
252 .. variable:: innodb_x_lock_os_waits
253
254- :version 5.5.8-20.0: Introduced.
255+ :version 5.6.11-60.3: Introduced.
256 :vartype: Numeric
257 :scope: Global
258
259 .. variable:: innodb_x_lock_spin_rounds
260
261- :version 5.5.8-20.0: Introduced.
262+ :version 5.6.11-60.3: Introduced.
263 :vartype: Numeric
264 :scope: Global
265
266 .. variable:: innodb_x_lock_spin_waits
267
268- :version 5.5.8-20.0: Introduced.
269+ :version 5.6.11-60.3: Introduced.
270 :vartype: Numeric
271 :scope: Global
272
273 INSERT BUFFER AND ADAPTIVE HASH INDEX
274 -------------------------------------
275
276-The 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: ::
277+The following variables contain information in the INSERT BUFFER AND ADAPTIVE HASH INDEX section of the output from ``SHOW ENGINE INNODB STATUS``. An example of that output is: ::
278
279 -------------------------------------
280 INSERT BUFFER AND ADAPTIVE HASH INDEX
281 -------------------------------------
282 Ibuf: size 1, free list len 6089, seg size 6091,
283 44497 inserts, 44497 merged recs, 8734 merges
284- Hash table size 276707, node heap has 1 buffer(s)
285 0.00 hash searches/s, 0.00 non-hash searches/s
286
287 .. variable:: innodb_ibuf_discarded_delete_marks
288
289- :version 5.5.8-20.0: Introduced.
290+ :version 5.6.11-60.3: Introduced.
291 :vartype: Numeric
292 :scope: Global
293
294 .. variable:: innodb_ibuf_discarded_deletes
295
296- :version 5.5.8-20.0: Introduced.
297+ :version 5.6.11-60.3: Introduced.
298 :vartype: Numeric
299 :scope: Global
300
301 .. variable:: innodb_ibuf_discarded_inserts
302
303- :version 5.5.8-20.0: Introduced.
304+ :version 5.6.11-60.3: Introduced.
305 :vartype: Numeric
306 :scope: Global
307
308 .. variable:: innodb_ibuf_free_list
309
310- :version 5.5.8-20.0: Introduced.
311+ :version 5.6.11-60.3: Introduced.
312 :vartype: Numeric
313 :scope: Global
314
315 .. variable:: innodb_ibuf_merged_delete_marks
316
317- :version 5.5.8-20.0: Introduced.
318+ :version 5.6.11-60.3: Introduced.
319 :vartype: Numeric
320 :scope: Global
321
322 .. variable:: innodb_ibuf_merged_deletes
323
324- :version 5.5.8-20.0: Introduced.
325+ :version 5.6.11-60.3: Introduced.
326 :vartype: Numeric
327 :scope: Global
328
329 .. variable:: innodb_ibuf_merged_inserts
330
331- :version 5.5.8-20.0: Introduced.
332+ :version 5.6.11-60.3: Introduced.
333 :vartype: Numeric
334 :scope: Global
335
336 .. variable:: innodb_ibuf_merges
337
338- :version 5.5.8-20.0: Introduced.
339+ :version 5.6.11-60.3: Introduced.
340 :vartype: Numeric
341 :scope: Global
342
343 .. variable:: innodb_ibuf_segment_size
344
345- :version 5.5.8-20.0: Introduced.
346+ :version 5.6.11-60.3: Introduced.
347 :vartype: Numeric
348 :scope: Global
349
350 .. variable:: innodb_ibuf_size
351
352- :version 5.5.8-20.0: Introduced.
353- :vartype: Numeric
354- :scope: Global
355-
356-.. variable:: innodb_adaptive_hash_cells
357-
358- :version 5.5.8-20.0: Introduced.
359- :vartype: Numeric
360- :scope: Global
361-
362-.. variable:: innodb_adaptive_hash_heap_buffers
363-
364- :version 5.5.8-20.0: Introduced.
365- :vartype: Numeric
366- :scope: Global
367-
368-.. variable:: innodb_adaptive_hash_hash_searches
369-
370- :version 5.5.8-20.0: Introduced.
371- :vartype: Numeric
372- :scope: Global
373-
374-.. variable:: innodb_adaptive_hash_non_hash_searches
375-
376- :version 5.5.8-20.0: Introduced.
377+ :version 5.6.11-60.3: Introduced.
378 :vartype: Numeric
379 :scope: Global
380
381 LOG
382 ---
383
384-The following variables contain information in the LOG section of the output from ``SHOW INNODB STATUS``. An example of that output is: ::
385+The following variables contain information in the LOG section of the output from ``SHOW ENGINE INNODB STATUS``. An example of that output is: ::
386
387- ---
388 LOG
389 ---
390- Log sequence number 28219393219
391- Log flushed up to 28219393219
392- Last checkpoint at 28212583337
393- Max checkpoint age 7782360
394- Checkpoint age target 7539162
395- Modified age 6809882
396- Checkpoint age 6809882
397+ Log sequence number 10145937666
398+ Log flushed up to 10145937666
399+ Pages flushed up to 10145937666
400+ Last checkpoint at 10145937666
401+ Max checkpoint age 80826164
402+ Checkpoint age target 78300347
403+ Modified age 0
404+ Checkpoint age 0
405 0 pending log writes, 0 pending chkp writes
406- 8570 log i/o's done, 2000.00 log i/o's/second
407+ 9 log i/o's done, 0.00 log i/o's/second
408+ Log tracking enabled
409+ Log tracked up to 10145937666
410+ Max tracked LSN age 80826164
411
412 .. variable:: innodb_lsn_current
413
414- :version 5.5.8-20.0: Introduced.
415+ :version 5.6.11-60.3: Introduced.
416 :vartype: Numeric
417 :scope: Global
418
419 .. variable:: innodb_lsn_flushed
420
421- :version 5.5.8-20.0: Introduced.
422+ :version 5.6.11-60.3: Introduced.
423 :vartype: Numeric
424 :scope: Global
425
426 .. variable:: innodb_lsn_last_checkpoint
427
428- :version 5.5.8-20.0: Introduced.
429+ :version 5.6.11-60.3: Introduced.
430 :vartype: Numeric
431 :scope: Global
432
433 .. variable:: innodb_checkpoint_age
434
435- :version 5.5.8-20.0: Introduced.
436+ :version 5.6.11-60.3: Introduced.
437 :vartype: Numeric
438 :scope: Global
439
440 .. variable:: innodb_checkpoint_max_age
441
442- :version 5.5.8-20.0: Introduced.
443- :vartype: Numeric
444- :scope: Global
445-
446-.. variable:: innodb_checkpoint_target_age
447-
448- :version 5.5.8-20.0: Introduced.
449+ :version 5.6.11-60.3: Introduced.
450 :vartype: Numeric
451 :scope: Global
452
453 BUFFER POOL AND MEMORY
454 ----------------------
455
456-The following variables contain information in the BUFFER POOL AND MEMORY section of the output from ``SHOW INNODB STATUS``. An example of that output is: ::
457+The following variables contain information in the BUFFER POOL AND MEMORY section of the output from ``SHOW ENGINE INNODB STATUS``. An example of that output is: ::
458
459 ----------------------
460 BUFFER POOL AND MEMORY
461 ----------------------
462- Total memory allocated 137625600; in additional pool allocated 0
463+ Total memory allocated 137363456; in additional pool allocated 0
464+ Total memory allocated by read views 88
465 Internal hash tables (constant factor + variable factor)
466- Adaptive hash index 3774352 (2213656 + 1560696)
467- Page hash 139144
468- Dictionary cache 629811 (554864 + 74947)
469- File system 83536 (82672 + 864)
470- Lock system 380792 (332872 + 47920)
471- Recovery system 0 (0 + 0)
472- Threads 84040 (82696 + 1344)
473- Dictionary memory allocated 74947
474- Buffer pool size 8192
475- Buffer pool size, bytes 134217728
476- Free buffers 0
477- Database pages 8095
478- Old database pages 2968
479- Modified db pages 5914
480+ Adaptive hash index 2266736 (2213368 + 53368)
481+ Page hash 139112 (buffer pool 0 only)
482+ Dictionary cache 729463 (554768 + 174695)
483+ File system 824800 (812272 + 12528)
484+ Lock system 333248 (332872 + 376)
485+ Recovery system 0 (0 + 0)
486+ Dictionary memory allocated 174695
487+ Buffer pool size 8191
488+ Buffer pool size, bytes 134201344
489+ Free buffers 7481
490+ Database pages 707
491+ Old database pages 280
492+ Modified db pages 0
493 Pending reads 0
494- Pending writes: LRU 0, flush list 129, single page 0
495- Pages made young 372084, not young 0
496- 2546000.00 youngs/s, 0.00 non-youngs/s
497- Pages read 103356, created 154787, written 979572
498- 469000.00 reads/s, 78000.00 creates/s, 138000.00 writes/s
499- Buffer pool hit rate 994 / 1000, young-making rate 34 / 1000 not 0 / 1000
500- Pages read ahead 0.00/s, evicted without access 15000.00/s
501+ Pending writes: LRU 0, flush list 0 single page 0
502+ Pages made young 0, not young 0
503+ 0.00 youngs/s, 0.00 non-youngs/s
504+ Pages read 707, created 0, written 1
505+ 0.00 reads/s, 0.00 creates/s, 0.00 writes/s
506+ No buffer pool page gets since the last printout
507+ Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
508+ LRU len: 707, unzip_LRU len: 0
509+
510
511 .. variable:: innodb_mem_adaptive_hash
512
513- :version 5.5.8-20.0: Introduced.
514+ :version 5.6.11-60.3: Introduced.
515 :vartype: Numeric
516 :scope: Global
517
518 .. variable:: innodb_mem_dictionary
519
520- :version 5.5.8-20.0: Introduced.
521+ :version 5.6.11-60.3: Introduced.
522 :vartype: Numeric
523 :scope: Global
524
525 .. variable:: innodb_mem_total
526
527- :version 5.5.8-20.0: Introduced.
528+ :version 5.6.11-60.3: Introduced.
529 :vartype: Numeric
530 :scope: Global
531
532 .. variable:: innodb_buffer_pool_pages_LRU_flushed
533
534- :version 5.5.8-20.0: Introduced.
535+ :version 5.6.11-60.3: Introduced.
536 :vartype: Numeric
537 :scope: Global
538
539 .. variable:: innodb_buffer_pool_pages_made_not_young
540
541- :version 5.5.8-20.0: Introduced.
542+ :version 5.6.11-60.3: Introduced.
543 :vartype: Numeric
544 :scope: Global
545
546 .. variable:: innodb_buffer_pool_pages_made_young
547
548- :version 5.5.8-20.0: Introduced.
549+ :version 5.6.11-60.3: Introduced.
550 :vartype: Numeric
551 :scope: Global
552
553 .. variable:: innodb_buffer_pool_pages_old
554
555- :version 5.5.8-20.0: Introduced.
556+ :version 5.6.11-60.3: Introduced.
557 :vartype: Numeric
558 :scope: Global
559
560@@ -427,44 +379,63 @@
561 ---TRANSACTION F561FC, ACTIVE 29 sec, process no 993, OS thread id 140213152769808 updating or deleting
562 mysql tables in use 1, locked 1
563
564+
565 .. variable:: innodb_history_list_length
566
567- :version 5.5.8-20.0: Introduced.
568+ :version 5.6.11-60.3: Introduced.
569 :vartype: Numeric
570 :scope: Global
571
572 .. variable:: innodb_max_trx_id
573
574- :version 5.5.8-20.0: Introduced.
575+ :version 5.6.11-60.3: Introduced.
576 :vartype: Numeric
577 :scope: Global
578
579 .. variable:: innodb_oldest_view_low_limit_trx_id
580
581- :version 5.5.8-20.0: Introduced.
582+ :version 5.6.11-60.3: Introduced.
583 :vartype: Numeric
584 :scope: Global
585
586 .. variable:: innodb_purge_trx_id
587
588- :version 5.5.8-20.0: Introduced.
589+ :version 5.6.11-60.3: Introduced.
590 :vartype: Numeric
591 :scope: Global
592
593 .. variable:: innodb_purge_undo_no
594
595- :version 5.5.8-20.0: Introduced.
596+ :version 5.6.11-60.3: Introduced.
597 :vartype: Numeric
598 :scope: Global
599
600 .. variable:: innodb_current_row_locks
601
602- :version 5.5.8-20.0: Introduced.
603- :version 5.5.10-20.1: Renamed.
604+ :version 5.6.11-60.3: Introduced.
605 :vartype: Numeric
606 :scope: Global
607
608- This variable was named :variable:`innodb_row_lock_numbers` in release 5.5.8-20.0.
609+INFORMATION_SCHEMA Tables
610+=========================
611+
612+The following table contains information about the oldest active transaction in the system.
613+
614+.. table:: INFORMATION_SCHEMA.XTRADB_READ_VIEW
615+
616+ :column READ_VIEW_UNDO_NUMBER:
617+ :column READ_VIEW_LOW_LIMIT_TRX_NUMBER: This is the highest transactions number at the time the view was created.
618+ :column READ_VIEW_UPPER_LIMIT_TRX_ID: This is the highest transactions ID at the time the view was created. This means that it should not see newer transactions with IDs bigger than or equal to that value.
619+ :column READ_VIEW_LOW_LIMIT_TRX_ID: This is the latest committed transaction ID at the time the oldest view was created. This means that it should see all transactions with IDs smaller than or equal to that value.
620+
621+The following table contains information about the memory usage for InnoDB/XtraDB hash tables.
622+
623+.. table:: INFORMATION_SCHEMA.XTRADB_INTERNAL_HASH_TABLES
624+
625+ :column INTERNAL_HASH_TABLE_NAME: Hash table name
626+ :column TOTAL_MEMORY: Total amount of memory
627+ :column CONSTANT_MEMORY: Constant memory
628+ :column VARIABLE_MEMORY: Variable memory
629
630
631 Other reading
632
633=== modified file 'doc/source/diagnostics/misc_info_schema_tables.rst'
634--- doc/source/diagnostics/misc_info_schema_tables.rst 2013-05-27 13:59:13 +0000
635+++ doc/source/diagnostics/misc_info_schema_tables.rst 2013-06-03 10:03:31 +0000
636@@ -46,3 +46,43 @@
637 :column UPDATE_TIME: Date and time of the latest update of the temporary table
638
639 This table holds information on the temporary tables existing for the running connection.
640+
641+Multiple Rollback Segments
642+==========================
643+
644+|Percona Server|, in addition to the upstream multiple rollback segment implementation, provides the additional Information Schema table: INFORMATION_SCHEMA.XTRADB_RSEG.
645+
646+``INFORMATION_SCHEMA`` Tables
647+=============================
648+
649+This feature provides the following table:
650+
651+.. table:: INFORMATION_SCHEMA.XTRADB_RSEG
652+
653+ :column rseg_id: rollback segment id
654+ :column space_id: space where the segment placed
655+ :column zip_size: compressed page size in bytes if compressed otherwise 0
656+ :column page_no: page number of the segment header
657+ :column max_size: max size in pages
658+ :column curr_size: current size in pages
659+
660+This table shows information about all the rollback segments (the default segment and the extra segments).
661+
662+Here is an example of output with ``innodb_extra_rsegments = 8`` ::
663+
664+ mysql> select * from information_schema.innodb_rseg;
665+ +---------+----------+----------+---------+------------+-----------+
666+ | rseg_id | space_id | zip_size | page_no | max_size | curr_size |
667+ +---------+----------+----------+---------+------------+-----------+
668+ | 0 | 0 | 0 | 6 | 4294967294 | 1 |
669+ | 1 | 0 | 0 | 13 | 4294967294 | 2 |
670+ | 2 | 0 | 0 | 14 | 4294967294 | 1 |
671+ | 3 | 0 | 0 | 15 | 4294967294 | 1 |
672+ | 4 | 0 | 0 | 16 | 4294967294 | 1 |
673+ | 5 | 0 | 0 | 17 | 4294967294 | 1 |
674+ | 6 | 0 | 0 | 18 | 4294967294 | 1 |
675+ | 7 | 0 | 0 | 19 | 4294967294 | 1 |
676+ | 8 | 0 | 0 | 20 | 4294967294 | 1 |
677+ +---------+----------+----------+---------+------------+-----------+
678+ 9 rows in set (0.00 sec)
679+
680
681=== modified file 'doc/source/diagnostics/mysql_syslog.rst'
682--- doc/source/diagnostics/mysql_syslog.rst 2013-05-27 13:46:13 +0000
683+++ doc/source/diagnostics/mysql_syslog.rst 2013-06-03 10:03:31 +0000
684@@ -9,8 +9,8 @@
685 Version Specific Information
686 ============================
687
688- * :rn:`5.5.8-20.0`:
689- Full functionality available.
690+ * :rn:`5.6.11-60.3`:
691+ Feature ported from |Percona Server| 5.5.
692
693 Other Information
694 =================
695
696=== modified file 'doc/source/diagnostics/show_engines.rst'
697--- doc/source/diagnostics/show_engines.rst 2013-05-27 13:59:13 +0000
698+++ doc/source/diagnostics/show_engines.rst 2013-06-03 10:03:31 +0000
699@@ -29,12 +29,6 @@
700 Version-Specific Information
701 ============================
702
703- * 5.5.8-20.0:
704+ * :rn:`5.6.11-60.3`:
705 Full functionality available.
706
707-Other Information
708-=================
709-
710- * Author / Origin:
711- Percona
712-
713
714=== added file 'doc/source/diagnostics/slow_extended.rst'
715--- doc/source/diagnostics/slow_extended.rst 1970-01-01 00:00:00 +0000
716+++ doc/source/diagnostics/slow_extended.rst 2013-06-03 10:03:31 +0000
717@@ -0,0 +1,355 @@
718+.. _slow_extended:
719+
720+================
721+ Slow Query Log
722+================
723+
724+This 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.
725+
726+You 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.
727+
728+
729+Version Specific Information
730+============================
731+
732+ * :rn:`5.6.11-60.3`:
733+
734+ * Feature ported from |Percona Server| 5.5.
735+
736+Other Information
737+=================
738+
739+ * Author / Origin:
740+ Maciej Dobrzanski
741+
742+System Variables
743+================
744+
745+.. variable:: log_slow_filter
746+
747+ :cli: Yes
748+ :conf: Yes
749+ :scope: Global, Session
750+ :dyn: Yes
751+
752+Filters the slow log by the query's execution plan. The value is a comma-delimited string, and can contain any combination of the following values:
753+
754+ * ``qc_miss``:
755+ The query was not found in the query cache.
756+
757+ * ``full_scan``:
758+ The query performed a full table scan.
759+
760+ * ``full_join``:
761+ The query performed a full join (a join without indexes).
762+
763+ * ``tmp_table``:
764+ The query created an implicit internal temporary table.
765+
766+ * ``tmp_table_on_disk``:
767+ The query's temporary table was stored on disk.
768+
769+ * ``filesort``:
770+ The query used a filesort.
771+
772+ * ``filesort_on_disk``:
773+ The filesort was performed on disk.
774+
775+Values 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.
776+
777+For 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``.
778+
779+.. variable:: log_slow_rate_type
780+
781+ :cli: Yes
782+ :conf: Yes
783+ :scope: Global
784+ :dyn: Yes
785+ :vartype: Enumerated
786+ :default: ``session``
787+ :range: ``session``, ``query``
788+
789+Specifies semantic of :variable:`log_slow_rate_limit` - ``session`` or ``query``.
790+
791+.. variable:: log_slow_rate_limit
792+
793+ :cli: Yes
794+ :conf: Yes
795+ :scope: Global, session
796+ :dyn: Yes
797+
798+Behavior of this variable depends from :variable:`log_slow_rate_type`.
799+
800+Specifies 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.
801+
802+Logging all queries might consume I/O bandwidth and cause the log file to grow large.
803+ * 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.
804+
805+ * 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 percent of queries will be logged.
806+
807+Note that every query has global unique ``query_id`` and every connection can has it own (session) :variable:`log_slow_rate_limit`.
808+Decision "log or no" calculated in following manner:
809+
810+ * if ``log_slow_rate_limit`` is 0 - log every query
811+
812+ * If ``log_slow_rate_limit`` > 0 - log query when (``query_id`` % ``log_slow_rate_limit``) is zero.
813+
814+This allows flexible setup logging behavior.
815+
816+For example, if you set the value to 100, then one percent of ``sessions/queries`` will be logged.
817+
818+.. variable:: log_slow_sp_statements
819+
820+ :cli: Yes
821+ :conf: Yes
822+ :scope: Global
823+ :dyn: Yes
824+ :vartype: Boolean
825+ :default: TRUE
826+ :range: TRUE/FALSE
827+
828+If ``TRUE``, statements executed by stored procedures are logged to the slow if it is open.
829+
830+.. note::
831+
832+ Support for logging stored procedures doesn't involve triggers, so they won't be logged even if this feature is enabled.
833+
834+.. variable:: log_slow_verbosity
835+
836+ :cli: Yes
837+ :conf: Yes
838+ :scope: Global, session
839+ :dyn: Yes
840+
841+Specifies 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:
842+
843+ * ``microtime``:
844+ Log queries with microsecond precision.
845+
846+ * ``query_plan``:
847+ Log information about the query's execution plan.
848+
849+ * ``innodb``:
850+ Log |InnoDB| statistics.
851+
852+ * ``minimal``:
853+ Equivalent to enabling just ``microtime``.
854+
855+ * ``standard``:
856+ Equivalent to enabling ``microtime,innodb``.
857+
858+ * ``full``:
859+ Equivalent to all other values OR'ed together.
860+
861+ * ``profiling``:
862+ Enables profiling of all queries in all connections.
863+
864+ * ``profiling_use_getrusage``:
865+ Enables usage of the getrusage function.
866+
867+Values are OR'ed together.
868+
869+For 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``.
870+
871+.. variable:: slow_query_log_timestamp_always
872+
873+ :cli: Yes
874+ :conf: Yes
875+ :scope: Global
876+ :dyn: Yes
877+ :vartype: Boolean
878+ :default: FALSE
879+ :range: TRUE/FALSE
880+
881+If ``TRUE``, a timestamp is printed on every slow log record. Multiple records may have the same time.
882+
883+.. variable:: slow_query_log_timestamp_precision
884+
885+ :cli: Yes
886+ :conf: Yes
887+ :scope: Global
888+ :dyn: Yes
889+ :vartype: Enumerated
890+ :default: ``second``
891+ :range: ``second``, ``microsecond``
892+
893+Normally, entries to the slow query log are in seconds precision, in this format: ::
894+
895+ # Time: 090402 9:23:36 # User@Host: XXX @ XXX [10.X.X.X]
896+
897+If :variable:`slow_query_log_timestamp_precision` ``=microsecond``, entries to the slow query log are in microsecond precision, in this format: ::
898+
899+ # Time: 090402 9:23:36.123456 # User@Host: XXX @ XXX [10.X.X.X]
900+
901+.. variable:: slow_query_log_use_global_control
902+
903+ :cli: Yes
904+ :conf: Yes
905+ :scope: Global
906+ :dyn: Yes
907+ :default: None
908+
909+Specifies which variables have global scope instead of local. Value is a "flag" variable - you can specify multiple values separated by commas
910+
911+ * ``none``:
912+ All variables use local scope
913+
914+ * ``log_slow_filter``:
915+ Global variable :variable:`log_slow_filter` has effect (instead of local)
916+
917+ * ``log_slow_rate_limit``:
918+ Global variable :variable:`log_slow_rate_limit` has effect (instead of local)
919+
920+ * ``log_slow_verbosity``:
921+ Global variable :variable:`log_slow_verbosity` has effect (instead of local)
922+
923+ * ``long_query_time``:
924+ Global variable :variable:`long_query_time` has effect (instead of local)
925+
926+ * ``min_examined_row_limit``:
927+ Global variable ``min_examined_row_limit`` has effect (instead of local)
928+
929+ * ``all``
930+ Global variables has effect (instead of local)
931+
932+
933+Other Information
934+=================
935+
936+Changes to the Log Format
937+-------------------------
938+
939+The feature adds more information to the slow log output. Here is a sample log entry: ::
940+
941+ # Time: 130601 8:01:06.058915
942+ # User@Host: root[root] @ localhost [] Id: 42
943+ # Schema: imdb Last_errno: 0 Killed: 0
944+ # Query_time: 7.725616 Lock_time: 0.000328 Rows_sent: 4 Rows_examined: 1543720 Rows_affected: 0
945+ # Bytes_sent: 272 Tmp_tables: 0 Tmp_disk_tables: 0 Tmp_table_sizes: 0
946+ # QC_Hit: No Full_scan: Yes Full_join: No Tmp_table: No Tmp_table_on_disk: No
947+ # Filesort: No Filesort_on_disk: No Merge_passes: 0
948+ SET timestamp=1370073666;
949+ SELECT id,title,production_year FROM title WHERE title = 'Bambi';
950+
951+
952+Another example (:variable:`log_slow_verbosity` ``=profiling``): ::
953+
954+ # Time: 130601 8:03:20.700441
955+ # User@Host: root[root] @ localhost [] Id: 43
956+ # Schema: imdb Last_errno: 0 Killed: 0
957+ # Query_time: 7.815071 Lock_time: 0.000261 Rows_sent: 4 Rows_examined: 1543720 Rows_affected: 0
958+ # Bytes_sent: 272
959+ # Profile_starting: 0.000125 Profile_starting_cpu: 0.000120
960+ Profile_checking_permissions: 0.000021 Profile_checking_permissions_cpu: 0.000021
961+ Profile_Opening_tables: 0.000049 Profile_Opening_tables_cpu: 0.000048 Profile_init: 0.000048
962+ Profile_init_cpu: 0.000049 Profile_System_lock: 0.000049 Profile_System_lock_cpu: 0.000048
963+ Profile_optimizing: 0.000024 Profile_optimizing_cpu: 0.000024 Profile_statistics: 0.000036
964+ Profile_statistics_cpu: 0.000037 Profile_preparing: 0.000029 Profile_preparing_cpu: 0.000029
965+ Profile_executing: 0.000012 Profile_executing_cpu: 0.000012 Profile_Sending_data: 7.814583
966+ Profile_Sending_data_cpu: 7.811634 Profile_end: 0.000013 Profile_end_cpu: 0.000012
967+ Profile_query_end: 0.000014 Profile_query_end_cpu: 0.000014 Profile_closing_tables: 0.000023
968+ Profile_closing_tables_cpu: 0.000023 Profile_freeing_items: 0.000051
969+ Profile_freeing_items_cpu: 0.000050 Profile_logging_slow_query: 0.000006
970+ Profile_logging_slow_query_cpu: 0.000006
971+ # Profile_total: 7.815085 Profile_total_cpu: 7.812127
972+ SET timestamp=1370073800;
973+ SELECT id,title,production_year FROM title WHERE title = 'Bambi';
974+
975+
976+Connection and Schema Identifier
977+--------------------------------
978+
979+Each 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.
980+
981+Each entry also contains a schema name, so you can trace all the queries whose default database was set to a particular schema. ::
982+
983+ # Id: 43 Schema: imdb
984+
985+Microsecond Time Resolution and Extra Row Information
986+-----------------------------------------------------
987+
988+This is the original functionality offered by the ``microslow`` feature. ``Query_time`` and ``Lock_time`` are logged with microsecond resolution.
989+
990+The feature also adds information about how many rows were examined for ``SELECT`` queries, and how many were analyzed and affected for ``UPDATE``, ``DELETE``, and ``INSERT`` queries, ::
991+
992+ # Query_time: 0.962742 Lock_time: 0.000202 Rows_sent: 4 Rows_examined: 1543719 Rows_affected: 0
993+
994+Values and context:
995+
996+ * ``Rows_examined``:
997+ Number of rows scanned - ``SELECT``
998+
999+ * ``Rows_affected``:
1000+ Number of rows changed - ``UPDATE``, ``DELETE``, ``INSERT``
1001+
1002+Memory Footprint
1003+----------------
1004+
1005+The feature provides information about the amount of bytes sent for the result of the query and the number of temporary tables created for its execution - differentiated by whether they were created on memory or on disk - with the total number of bytes used by them. ::
1006+
1007+ # Bytes_sent: 8053 Tmp_tables: 1 Tmp_disk_tables: 0 Tmp_table_sizes: 950528
1008+
1009+Values and context:
1010+
1011+ * ``Bytes_sent``:
1012+ The amount of bytes sent for the result of the query
1013+
1014+ * ``Tmp_tables``:
1015+ Number of temporary tables created on memory for the query
1016+
1017+ * ``Tmp_disk_tables``:
1018+ Number of temporary tables created on disk for the query
1019+
1020+ * ``Tmp_table_sizes``:
1021+ Total Size in bytes for all temporary tables used in the query
1022+
1023+
1024+Query Plan Information
1025+----------------------
1026+
1027+Each query can be executed in various ways. For example, it may use indexes or do a full table scan, or a temporary table may be needed. These are the things that you can usually see by running ``EXPLAIN`` on the query. The feature will now allow you to see the most important facts about the execution in the log file. ::
1028+
1029+ # QC_Hit: No Full_scan: Yes Full_join: No Tmp_table: No Tmp_table_on_disk: No
1030+ # Filesort: No Filesort_on_disk: No Merge_passes: 0
1031+
1032+The values and their meanings are documented with the :variable:`log_slow_filter` option.
1033+
1034+|InnoDB| Usage Information
1035+--------------------------
1036+
1037+The final part of the output is the |InnoDB| usage statistics. |MySQL| currently shows many per-session statistics for operations with ``SHOW SESSION STATUS``, but that does not include those of |InnoDB|, which are always global and shared by all threads. This feature lets you see those values for a given query. ::
1038+
1039+ # InnoDB_IO_r_ops: 6415 InnoDB_IO_r_bytes: 105103360 InnoDB_IO_r_wait: 0.001279
1040+ # InnoDB_rec_lock_wait: 0.000000 InnoDB_queue_wait: 0.000000
1041+ # InnoDB_pages_distinct: 6430
1042+
1043+Values:
1044+
1045+ * ``innodb_IO_r_ops``:
1046+ 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.
1047+
1048+ * ``innodb_IO_r_bytes``:
1049+ Similar to innodb_IO_r_ops, but the unit is bytes.
1050+
1051+ * ``innodb_IO_r_wait``:
1052+ Shows how long (in seconds) it took |InnoDB| to actually read the data from storage.
1053+
1054+ * ``innodb_rec_lock_wait``:
1055+ Shows how long (in seconds) the query waited for row locks.
1056+
1057+ * ``innodb_queue_wait``:
1058+ Shows how long (in seconds) the query spent either waiting to enter the |InnoDB| queue or inside that queue waiting for execution.
1059+
1060+ * ``innodb_pages_distinct``:
1061+ 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.
1062+
1063+If the query did not use |InnoDB| tables, that information is written into the log instead of the above statistics.
1064+
1065+Related Reading
1066+===============
1067+
1068+ * `Impact of logging on MySQL's performance <http://www.mysqlperformanceblog.com/2009/02/10/impact-of-logging-on-mysql%E2%80%99s-performance/>`_
1069+
1070+ * `log_slow_filter Usage <http://www.mysqlperformanceblog.com/2008/09/22/finding-what-created_tmp_disk_tables-with-log_slow_filter/>`_
1071+
1072+ * `Blueprint in Launchpad <https://blueprints.launchpad.net/percona-server/+spec/microseconds-in-query-log>`_
1073
1074=== removed file 'doc/source/diagnostics/slow_extended_55.rst'
1075--- doc/source/diagnostics/slow_extended_55.rst 2013-05-10 09:39:17 +0000
1076+++ doc/source/diagnostics/slow_extended_55.rst 1970-01-01 00:00:00 +0000
1077@@ -1,377 +0,0 @@
1078-.. _slow_extended_55:
1079-
1080-================
1081- Slow Query Log
1082-================
1083-
1084-This 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.
1085-
1086-The 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|.
1087-
1088-You 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.
1089-
1090-
1091-Version Specific Information
1092-============================
1093-
1094- * 5.5.8-20.0:
1095- Added values ``profiling`` and ``profiling_use_getrusage`` to variable log_slow_verbosity.
1096-
1097- * 5.5.10-20.1:
1098- * Renamed variable :variable:`slow_query_log_timestamp_always` to :variable:`slow_query_log_timestamp_always`.
1099-
1100- * Renamed variable :variable:`slow_query_log_microseconds_timestamp` to :variable:`slow_query_log_timestamp_precision`.
1101-
1102- * Renamed variable :variable:`use_global_log_slow_control` to :variable:`slow_query_log_use_global_control`.
1103-
1104-Other Information
1105-=================
1106-
1107- * Author / Origin:
1108- Maciej Dobrzanski, Percona
1109-
1110-System Variables
1111-================
1112-
1113-.. variable:: log_slow_admin_statements
1114-
1115- :cli: Yes
1116- :conf: Yes
1117- :scope: Global
1118- :dyn: yes
1119-
1120-When 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.
1121-
1122-.. variable:: log_slow_filter
1123-
1124- :cli: Yes
1125- :conf: Yes
1126- :scope: Global, Session
1127- :dyn: Yes
1128-
1129-Filters the slow log by the query's execution plan. The value is a comma-delimited string, and can contain any combination of the following values:
1130-
1131- * ``qc_miss``:
1132- The query was not found in the query cache.
1133-
1134- * ``full_scan``:
1135- The query performed a full table scan.
1136-
1137- * ``full_join``:
1138- The query performed a full join (a join without indexes).
1139-
1140- * ``tmp_table``:
1141- The query created an implicit internal temporary table.
1142-
1143- * ``tmp_table_on_disk``:
1144- The query``s temporary table was stored on disk.
1145-
1146- * ``filesort``:
1147- The query used a filesort.
1148-
1149- * ``filesort_on_disk``:
1150- The filesort was performed on disk.
1151-
1152-Values 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.
1153-
1154-For 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``.
1155-
1156-.. variable:: log_slow_rate_type
1157-
1158- :cli: Yes
1159- :conf: Yes
1160- :scope: Global
1161- :dyn: Yes
1162- :vartype: Enumerated
1163- :default: ``session``
1164- :range: ``session``, ``query``
1165-
1166-Specifies semantic of :variable:`log_slow_rate_limit` - ``session`` or ``query``.
1167-
1168-.. variable:: log_slow_rate_limit
1169-
1170- :cli: Yes
1171- :conf: Yes
1172- :scope: Global, session
1173- :dyn: Yes
1174-
1175-Behavior of this variable depends from :variable:`log_slow_rate_type`.
1176-
1177-Specifies 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.
1178-
1179-Logging all queries might consume I/O bandwidth and cause the log file to grow large.
1180- * 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.
1181-
1182- * 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.
1183-
1184-Note that every query has global unique ``query_id`` and every connection can has it own (session) :variable:``log_slow_rate_limit``.
1185-Decision "log or no" calculated in following manner:
1186-
1187- * if ``log_slow_rate_limit`` is 0 - log every query
1188-
1189- * If ``log_slow_rate_limit`` > 0 - log query when (``query_id`` % ``log_slow_rate_limit``) is zero.
1190-
1191-This allows flexible setup logging behavior.
1192-
1193-For example, if you set the value to 100, then one percent of ``sessions/queries`` will be logged.
1194-
1195-.. variable:: log_slow_slave_statements
1196-
1197- :cli: Yes
1198- :conf: Yes
1199- :scope: Global, session
1200- :dyn: Yes (in 5.1 releases only)
1201-
1202-Specifies 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.
1203-
1204-To 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.
1205-
1206-To 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.
1207-
1208-
1209-.. variable:: log_slow_sp_statements
1210-
1211- :cli: Yes
1212- :conf: Yes
1213- :scope: Global
1214- :dyn: Yes
1215- :vartype: Boolean
1216- :default: TRUE
1217- :range: TRUE/FALSE
1218-
1219-If ``TRUE``, statements executed by stored procedures are logged to the slow if it is open.
1220-
1221-.. note::
1222-
1223- Support for logging stored procedures doesn't involve triggers, so they won't be logged even if this feature is enabled.
1224-
1225-.. variable:: log_slow_verbosity
1226-
1227- :version 5.5.8-20.0: Added ``profiling`` and ``profiling_use_getrusage``
1228- :cli: Yes
1229- :conf: Yes
1230- :scope: Global, session
1231- :dyn: Yes
1232-
1233-Specifies 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:
1234-
1235- * ``microtime``:
1236- Log queries with microsecond precision.
1237-
1238- * ``query_plan``:
1239- Log information about the query's execution plan.
1240-
1241- * ``innodb``:
1242- Log |InnoDB| statistics.
1243-
1244- * ``minimal``:
1245- Equivalent to enabling just ``microtime``.
1246-
1247- * ``standard``:
1248- Equivalent to enabling ``microtime,innodb``.
1249-
1250- * ``full``:
1251- Equivalent to all other values OR'ed together.
1252-
1253- * ``profiling``:
1254- Enables profiling of all queries in all connections.
1255-
1256- * ``profiling_use_getrusage``:
1257- Enables usage of the getrusage function.
1258-
1259-Values are OR'ed together.
1260-
1261-For 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``.
1262-
1263-.. variable:: slow_query_log_timestamp_always
1264-
1265- :version 5.5.10-20.1: Introduced (renamed from :variable:`log_slow_timestamp_every`)
1266- :cli: Yes
1267- :conf: Yes
1268- :scope: Global
1269- :dyn: Yes
1270- :vartype: Boolean
1271- :default: FALSE
1272- :range: TRUE/FALSE
1273-
1274-If ``TRUE``, a timestamp is printed on every slow log record. Multiple records may have the same time.
1275-
1276-.. variable:: slow_query_log_timestamp_precision
1277-
1278- :version 5.5.10-20.1: Introduced (renamed from ``slow_query_log_microseconds_timestamp``)
1279- :cli: Yes
1280- :conf: Yes
1281- :scope: Global
1282- :dyn: Yes
1283- :vartype: Enumerated
1284- :default: ``second``
1285- :range: ``second``, ``microsecond``
1286-
1287-Normally, entries to the slow query log are in seconds precision, in this format: ::
1288-
1289- # Time: 090402 9:23:36 # User@Host: XXX @ XXX [10.X.X.X]
1290-
1291-If :variable:`slow_query_log_timestamp_precision` ``=microsecond``, entries to the slow query log are in microsecond precision, in this format: ::
1292-
1293- # Time: 090402 9:23:36.123456 # User@Host: XXX @ XXX [10.X.X.X]
1294-
1295-.. variable:: slow_query_log_use_global_control
1296-
1297- :cli: Yes
1298- :conf: Yes
1299- :scope: Global
1300- :dyn: Yes
1301- :default: None
1302- :version 5.5.10-20.1: Introduced (renamed from :variable:`log_slow_timestamp_every`)
1303-
1304-Specifies which variables have global scope instead of local. Value is a “flag” variable - you can specify multiple values separated by commas
1305-
1306- * ``none``:
1307- All variables use local scope
1308-
1309- * ``log_slow_filter``:
1310- Global variable :variable:`log_slow_filter` has effect (instead of local)
1311-
1312- * ``log_slow_rate_limit``:
1313- Global variable :variable:`log_slow_rate_limit` has effect (instead of local)
1314-
1315- * ``log_slow_verbosity``:
1316- Global variable :variable:`log_slow_verbosity` has effect (instead of local)
1317-
1318- * ``long_query_time``:
1319- Global variable :variable:`long_query_time` has effect (instead of local)
1320-
1321- * ``min_examined_row_limit``:
1322- Global variable ``min_examined_row_limit`` has effect (instead of local)
1323-
1324- * ``all``
1325- Global variables has effect (instead of local)
1326-
1327-**NOTE:** This variable has been renamed from :variable:`log_slow_timestamp_every` since 5.5.10-20.1.
1328-
1329-
1330-Other Information
1331-=================
1332-
1333-Changes to the Log Format
1334--------------------------
1335-
1336-The feature adds more information to the slow log output. Here is a sample log entry: ::
1337-
1338- # User@Host: mailboxer[mailboxer] @ [192.168.10.165]
1339- # Thread_id: 11167745 Schema: board
1340- # QC_Hit: No Full_scan: No Full_join: No Tmp_table: Yes Disk_tmp_table: No
1341- # Filesort: Yes Disk_filesort: No Merge_passes: 0
1342- # Query_time: 0.000659 Lock_time: 0.000070 Rows_sent: 0 Rows_examined: 30 Rows_affected: 0 Rows_read: 30
1343- # innodb_IO_r_ops: 1 innodb_IO_r_bytes: 16384 innodb_IO_r_wait: 0.028487
1344- # innodb_rec_lock_wait: 0.000000 innodb_queue_wait: 0.000000
1345- # innodb_pages_distinct: 5
1346- select count(distinct author_id) from art87.article87 force index (forum_id) where forum_id = 240215 and thread_id = ``710575``
1347-
1348-Another example (:variable:`log_slow_verbosity` ``=profiling``): ::
1349-
1350- # Query_time: 4.555235 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 Rows_affected: 0 Rows_read: 1
1351- # 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
1352- # Profile_total: 4.555405 Profile_total_cpu: 0.000000
1353- insert into teee4 select * from teee4 limit 10000000;
1354-
1355-Connection and Schema Identifier
1356---------------------------------
1357-
1358-Each 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.
1359-
1360-Each entry also contains a schema name, so you can trace all the queries whose default database was set to a particular schema. ::
1361-
1362- # Thread_id: 11167745 Schema: board
1363-
1364-Microsecond Time Resolution and Extra Row Information
1365------------------------------------------------------
1366-
1367-This is the original functionality offered by the ``microslow`` feature. ``Query_time`` and ``Lock_time`` are logged with microsecond resolution.
1368-
1369-The feature also adds information about how many rows were examined for ``SELECT`` queries, and how many were analyzed and affected for ``UPDATE``, ``DELETE``, and ``INSERT`` queries, ::
1370-
1371- # Query_time: 0.000659 Lock_time: 0.000070 Rows_sent: 0 Rows_examined: 30 Rows_affected: 0 Rows_read: 30
1372-
1373-Values and context:
1374-
1375- * ``Rows_examined``:
1376- Number of rows scanned - ``SELECT``
1377-
1378- * ``Rows_affected``:
1379- Number of rows changed - ``UPDATE``, ``DELETE``, ``INSERT``
1380-
1381- * ``Rows_read``:
1382- Number of rows read - ``UPDATE``, ``DELETE``, ``INSERT``
1383-
1384-Memory Footprint
1385-----------------
1386-
1387-The feature provides information about the amount of bytes sent for the result of the query and the number of temporary tables created for its execution - differentiated by whether they were created on memory or on disk - with the total number of bytes used by them. ::
1388-
1389- # Bytes_sent: 8053 Tmp_tables: 1 Tmp_disk_tables: 0 Tmp_table_sizes: 950528
1390-
1391-Values and context:
1392-
1393- * ``Bytes_sent``:
1394- The amount of bytes sent for the result of the query
1395-
1396- * ``Tmp_tables``:
1397- Number of temporary tables created on memory for the query
1398-
1399- * ``Tmp_disk_tables``:
1400- Number of temporary tables created on disk for the query
1401-
1402- * ``Tmp_table_sizes``:
1403- Total Size in bytes for all temporary tables used in the query
1404-
1405-
1406-Query Plan Information
1407-----------------------
1408-
1409-Each query can be executed in various ways. For example, it may use indexes or do a full table scan, or a temporary table may be needed. These are the things that you can usually see by running ``EXPLAIN`` on the query. The feature will now allow you to see the most important facts about the execution in the log file. ::
1410-
1411- # QC_Hit: No Full_scan: No Full_join: No Tmp_table: Yes Disk_tmp_table: No
1412- # Filesort: Yes Disk_filesort: No Merge_passes: 0
1413-
1414-The values and their meanings are documented with the :variable:`log_slow_filter` option.
1415-
1416-|InnoDB| Usage Information
1417---------------------------
1418-
1419-The final part of the output is the |InnoDB| usage statistics. |MySQL| currently shows many per-session statistics for operations with ``SHOW SESSION STATUS``, but that does not include those of |InnoDB|, which are always global and shared by all threads. This feature lets you see those values for a given query. ::
1420-
1421- # innodb_IO_r_ops: 1 innodb_IO_r_bytes: 16384 innodb_IO_r_wait: 0.028487
1422- # innodb_rec_lock_wait: 0.000000 innodb_queue_wait: 0.000000
1423- # innodb_pages_distinct: 5
1424-
1425-Values:
1426-
1427- * ``innodb_IO_r_ops``:
1428- 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.
1429-
1430- * ``innodb_IO_r_bytes``:
1431- Similar to innodb_IO_r_ops, but the unit is bytes.
1432-
1433- * ``innodb_IO_r_wait``:
1434- Shows how long (in seconds) it took |InnoDB| to actually read the data from storage.
1435-
1436- * ``innodb_rec_lock_wait``:
1437- Shows how long (in seconds) the query waited for row locks.
1438-
1439- * ``innodb_queue_wait``:
1440- Shows how long (in seconds) the query spent either waiting to enter the |InnoDB| queue or inside that queue waiting for execution.
1441-
1442- * ``innodb_pages_distinct``:
1443- 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.
1444-
1445-If the query did not use |InnoDB| tables, that information is written into the log instead of the above statistics.
1446-
1447-Related Reading
1448-===============
1449-
1450- * http://www.mysqlperformanceblog.com/2009/02/10/impact-of-logging-on-mysql%E2%80%99s-performance/
1451-
1452- * `log_slow_filter Usage <http://www.mysqlperformanceblog.com/2008/09/22/finding-what-created_tmp_disk_tables-with-log_slow_filter/>`_
1453-
1454- * `Blueprint in Launchpad <https://blueprints.launchpad.net/percona-server/+spec/microseconds-in-query-log>`_
1455
1456=== modified file 'doc/source/diagnostics/thread_based_profiling.rst'
1457--- doc/source/diagnostics/thread_based_profiling.rst 2012-09-18 05:04:43 +0000
1458+++ doc/source/diagnostics/thread_based_profiling.rst 2013-06-03 10:03:31 +0000
1459@@ -13,5 +13,5 @@
1460 Version Specific Information
1461 ============================
1462
1463- * :rn:`5.5.25a-27.1`:
1464- Thread based profiling introduced
1465+ * :rn:`5.6.11-60.3`:
1466+ Thread based profiling ported from |Percona Server| 5.5.
1467
1468=== modified file 'doc/source/diagnostics/user_stats.rst'
1469--- doc/source/diagnostics/user_stats.rst 2013-05-27 13:59:13 +0000
1470+++ doc/source/diagnostics/user_stats.rst 2013-06-03 10:03:31 +0000
1471@@ -12,21 +12,21 @@
1472 Version Specific Information
1473 ============================
1474
1475- * :rn:`5.5.10-20.1`:
1476- Renamed variable :variable:`userstat_running` to :variable:`userstat`.
1477+ * :rn:`5.6.11-60.3`:
1478+ Feature ported from |Percona Server| 5.5.
1479
1480 Other Information
1481 =================
1482
1483 * Author/Origin:
1484- *Google*; *Percona* added the ``INFORMATION_SCHEMA`` tables and the :variable:`userstat_running` variable.
1485+ *Google*; *Percona* added the ``INFORMATION_SCHEMA`` tables and the :variable:`userstat` variable.
1486
1487 System Variables
1488 ================
1489
1490-.. variable:: userstat_running
1491+.. variable:: userstat
1492
1493- :version 5.5.10-20.1: Renamed to :variable:`userstat`
1494+ :version 5.6.11-60.3: Variable introduced
1495 :cli: Yes
1496 :conf: Yes
1497 :scope: Global
1498
1499=== removed file 'doc/source/flexibility/buff_read_ahead_area.rst'
1500--- doc/source/flexibility/buff_read_ahead_area.rst 2013-05-27 13:46:13 +0000
1501+++ doc/source/flexibility/buff_read_ahead_area.rst 1970-01-01 00:00:00 +0000
1502@@ -1,36 +0,0 @@
1503-.. _buff_read_ahead_area:
1504-
1505-====================================
1506- Fixed Size for the Read Ahead Area
1507-====================================
1508-
1509-|InnoDB| dynamically calculates the size of the read-ahead area in case it has to trigger its read-ahead algorithm. When the workload involves heavy I/O operations, this size is computed so frequently that it has a non-negligeable impact on the CPU usage.
1510-
1511-This variable only depends on the size of the buffer pool set by the :variable:`innodb_buffer_pool_size` variable, and as soon as the buffer pool has a size properly greater than 1024 pages (or 16 MB), it is always 64. With this change, its value is fixed to 64, thus removing a bottleneck experienced by some users.
1512-
1513-Please note that the minimum allowed value for the |InnoDB| buffer pool is de facto set to 32 MB.
1514-
1515-This change is a port of the feature from Facebook:
1516-
1517- * http://bazaar.launchpad.net/~mysqlatfacebook/mysqlatfacebook/5.1/revision/3538
1518-
1519-
1520-Version Specific Information
1521-============================
1522-
1523- * :rn:`5.5.8-20.0` :
1524- Full functionality available.
1525-
1526-Other Information
1527-=================
1528-
1529- * Author/Origin:
1530- Facebook
1531-
1532- * Bugs fixed:
1533- :bug:`606811`
1534-
1535-Other Reading
1536-=============
1537-
1538- * `BUF_READ_AHEAD_AREA Bottleneck <http://www.facebook.com/notes/mysqlfacebook/using-pmp-to-double-mysql-throughput-part-2/405092575932>`_
1539
1540=== removed file 'doc/source/flexibility/innodb_files_extend.rst'
1541--- doc/source/flexibility/innodb_files_extend.rst 2013-05-26 07:09:29 +0000
1542+++ doc/source/flexibility/innodb_files_extend.rst 1970-01-01 00:00:00 +0000
1543@@ -1,25 +0,0 @@
1544-.. _innodb_files_extend:
1545-
1546-================================
1547- Support of Multiple Page Sizes
1548-================================
1549-
1550-In standard |InnoDB|, the size of the read-ahead area is computed dynamically, but it always has the same value. This change makes the size fixed, avoiding unuseful computations.
1551-
1552-This feature adds a new system variable for setting it.
1553-
1554-
1555-System Variables
1556-================
1557-
1558-.. variable:: innodb_page_size
1559-
1560- :cli: Yes
1561- :conf: Yes
1562- :scope:
1563- :dyn: No
1564- :vartype: ULONG
1565- :default: 1 « 14
1566- :range: 1 « 12 to 1 « ``UNIV_PAGE_SIZE_SHIFT_MAX``
1567-
1568-**EXPERIMENTAL**: The universal page size of the database. Changing for an existing database is not supported. Use at your own risk!
1569
1570=== modified file 'doc/source/flexibility/log_warnings_suppress.rst'
1571--- doc/source/flexibility/log_warnings_suppress.rst 2013-05-27 13:46:13 +0000
1572+++ doc/source/flexibility/log_warnings_suppress.rst 2013-06-03 10:03:31 +0000
1573@@ -10,11 +10,8 @@
1574 Version Specific Information
1575 ============================
1576
1577- * :rn:`5.5.8-20.0`:
1578- System variable :variable:`log_warnings_silence` introduced.
1579-
1580- * :rn:`5.5.10-20.1`:
1581- Renamed variable :variable:`log_warnings_silence` to :variable:`log_warnings_suppress`.
1582+ * :rn:`5.6.11-60.3`:
1583+ Variable :variable:`log_warnings_suppress` ported from |Percona Server| 5.5.
1584
1585
1586 System Variables
1587@@ -22,8 +19,7 @@
1588
1589 .. variable:: log_warnings_suppress
1590
1591- :version 5.5.8-20.0: Introduced.
1592- :version 5.5.10-20.1: Renamed.
1593+ :version 5.6.11-60.3: Introduced.
1594 :cli: Yes
1595 :conf: Yes
1596 :scope: Global
1597@@ -32,12 +28,8 @@
1598 :default: ``(empty string)``
1599 :range: ``(empty string)``, ``1592``
1600
1601-This variable was added in beta release ``5.5.8-20.0`` as :variable:`log_warnings_silence` and renamed in release 5.5.10-20.1.
1602-
1603 It is intended to provide a more general mechanism for disabling warnings than existed previously with variable :variable:`suppress_log_warning_1592`.
1604-
1605 When set to the empty string, no warnings are disabled. When set to ``1592``, warning #1592 messages (unsafe statement for binary logging) are suppressed.
1606-
1607 In the future, the ability to optionally disable additional warnings may also be added.
1608
1609
1610
1611=== modified file 'doc/source/flexibility/max_binlog_files.rst'
1612--- doc/source/flexibility/max_binlog_files.rst 2013-01-30 10:01:50 +0000
1613+++ doc/source/flexibility/max_binlog_files.rst 2013-06-03 10:03:31 +0000
1614@@ -11,7 +11,7 @@
1615 Version Specific Information
1616 ============================
1617
1618- * 5.5.27-29.0:
1619+ * 5.6.11-60.3:
1620 Variable :variable:`max_binlog_files` introduced.
1621
1622 System Variables
1623@@ -19,7 +19,7 @@
1624
1625 .. variable:: max_binlog_files
1626
1627- :version 5.5.27-29.0: Introduced.
1628+ :version 5.6.11-60.3: Introduced.
1629 :cli: Yes
1630 :conf: Yes
1631 :scope: Global
1632
1633=== modified file 'doc/source/index.rst'
1634--- doc/source/index.rst 2013-05-13 04:25:56 +0000
1635+++ doc/source/index.rst 2013-06-03 10:03:31 +0000
1636@@ -51,6 +51,15 @@
1637 installation
1638 upgrading_guide_55_56
1639
1640+Scalability Improvements
1641+========================
1642+
1643+.. toctree::
1644+ :maxdepth: 1
1645+ :glob:
1646+
1647+ scalability/innodb_io
1648+
1649 Performance Improvements
1650 ========================
1651
1652@@ -69,6 +78,9 @@
1653 :maxdepth: 1
1654 :glob:
1655
1656+ flexibility/log_warnings_suppress
1657+ flexibility/improved_memory_engine
1658+ flexibility/max_binlog_files
1659 flexibility/mysqldump_ignore_create_error
1660
1661 Reliability Improvements
1662@@ -81,6 +93,7 @@
1663 reliability/log_connection_error
1664 reliability/error_pad
1665 reliability/innodb_corrupt_table_action
1666+ reliability/show_slave_status_nolock
1667
1668 Management Improvements
1669 =======================
1670@@ -89,7 +102,7 @@
1671 :maxdepth: 1
1672 :glob:
1673
1674- management/udf_maatkit
1675+ management/udf_percona_toolkit
1676 management/innodb_fake_changes
1677 management/innodb_kill_idle_trx
1678 management/enforce_engine
1679@@ -107,16 +120,16 @@
1680 :maxdepth: 1
1681 :glob:
1682
1683- diagnostics/index_info_schema_tables
1684- diagnostics/innodb_stats
1685 diagnostics/user_stats
1686- diagnostics/slow_extended_55
1687+ diagnostics/slow_extended
1688 diagnostics/innodb_show_status
1689 diagnostics/innodb_deadlock_count
1690 diagnostics/mysql_syslog
1691 diagnostics/show_engines
1692+ diagnostics/innodb_show_lock_names
1693 diagnostics/process_list
1694 diagnostics/misc_info_schema_tables
1695+ diagnostics/thread_based_profiling
1696
1697 Reference
1698 =========
1699@@ -128,6 +141,7 @@
1700 upstream-bug-fixes
1701 development
1702 trademark-policy
1703+ index_info_schema_tables
1704 faq
1705 compatibility
1706 release-notes/release-notes_index
1707
1708=== modified file 'doc/source/index_info_schema_tables.rst'
1709--- doc/source/index_info_schema_tables.rst 2012-12-10 15:24:56 +0000
1710+++ doc/source/index_info_schema_tables.rst 2013-06-03 10:03:31 +0000
1711@@ -8,11 +8,11 @@
1712
1713 * :table:`CLIENT_STATISTICS`
1714
1715+ * :table:`GLOBAL_TEMPORARY_TABLES`
1716+
1717 * :table:`INDEX_STATISTICS`
1718
1719- * :table:`GLOBAL_TEMPORARY_TABLES`
1720-
1721- * :table:`QUERY_RESPONSE_TIME`
1722+ * :table:`INNODB_CHANGED_PAGES`
1723
1724 * :table:`TABLE_STATISTICS`
1725
1726@@ -22,37 +22,9 @@
1727
1728 * :table:`USER_STATISTICS`
1729
1730- * :table:`INNODB_RSEG`
1731-
1732- * :table:`INNODB_UNDO_LOGS`
1733-
1734- * :table:`INNODB_SYS_TABLESTATS`
1735-
1736- * :table:`INNODB_INDEX_STATS`
1737-
1738- * :table:`INNODB_CHANGED_PAGES`
1739-
1740- * :table:`INNODB_BUFFER_POOL_PAGES`
1741-
1742- * :table:`INNODB_BUFFER_POOL_PAGES_BLOB`
1743-
1744- * :table:`INNODB_BUFFER_POOL_PAGES_INDEX`
1745-
1746- * :table:`INNODB_SYS_TABLES`
1747-
1748- * :table:`INNODB_SYS_FIELDS`
1749-
1750- * :table:`INNODB_SYS_COLUMNS`
1751-
1752- * :table:`INNODB_SYS_STATS`
1753-
1754- * :table:`INNODB_SYS_FOREIGN`
1755-
1756- * :table:`INNODB_SYS_INDEXES`
1757-
1758- * :table:`XTRADB_ADMIN_COMMAND`
1759-
1760- * :table:`INNODB_TABLE_STATS`
1761-
1762- * :table:`INNODB_SYS_FOREIGN_COLS`
1763+ * :table:`XTRADB_INTERNAL_HASH_TABLES`
1764+
1765+ * :table:`XTRADB_READ_VIEW`
1766+
1767+ * :table:`XTRADB_RSEG`
1768
1769
1770=== modified file 'doc/source/installation.rst'
1771--- doc/source/installation.rst 2013-05-27 13:59:13 +0000
1772+++ doc/source/installation.rst 2013-06-03 10:03:31 +0000
1773@@ -201,4 +201,4 @@
1774
1775 .. note::
1776
1777- :ref:`pam_plugin` has been merged into |Percona Server| in :rn:`5.5.24-26.0` but it is not built with the server by default. In order to build the Percona Server with PAM plugin, additional option :option:`-DWITH_PAM=ON` should be used.
1778+ :ref:`pam_plugin` is not built with the server by default. In order to build the Percona Server with PAM plugin, additional option :option:`-DWITH_PAM=ON` should be used.
1779
1780=== modified file 'doc/source/management/changed_page_tracking.rst'
1781--- doc/source/management/changed_page_tracking.rst 2013-03-06 06:41:38 +0000
1782+++ doc/source/management/changed_page_tracking.rst 2013-06-03 10:03:31 +0000
1783@@ -18,7 +18,7 @@
1784 User statements for handling the XtraDB changed page bitmaps
1785 ============================================================
1786
1787-In |Percona Server| :rn:`5.5.29-30.0` new statements have been introduced for handling the changed page bitmap tracking. All of these statements require ``SUPER`` privilege.
1788+In |Percona Server| :rn:`5.6.11-60.3` new statements have been introduced for handling the changed page bitmap tracking. All of these statements require ``SUPER`` privilege.
1789
1790 * ``FLUSH CHANGED_PAGE_BITMAPS`` - this statement can be used for synchronous bitmap write for immediate catch-up with the log checkpoint. This is used by innobackupex to make sure that XtraBackup indeed has all the required data it needs.
1791 * ``RESET CHANGED_PAGE_BITMAPS`` - this statement will delete all the bitmap log files and restart the bitmap log file sequence.
1792@@ -52,8 +52,7 @@
1793
1794 .. variable:: innodb_max_changed_pages
1795
1796- :version 5.5.27-29.0: Variable :variable:`innodb_changed_pages_limit` introduced
1797- :version 5.5.29-30.0: Variable renamed to :variable:`innodb_max_changed_pages`
1798+ :version 5.6.11-60.3: Variable :variable:`innodb_max_changed_pages` introduced
1799 :cli: Yes
1800 :conf: Yes
1801 :scope: Global
1802@@ -64,7 +63,7 @@
1803
1804 .. variable:: innodb_track_changed_pages
1805
1806- :version 5.5.27-29.0: Variable introduced
1807+ :version 5.6.11-60.3: Variable introduced
1808 :cli: Yes
1809 :conf: Yes
1810 :scope: Global
1811@@ -75,7 +74,7 @@
1812
1813 .. variable:: innodb_max_bitmap_file_size
1814
1815- :version 5.5.28-29.2: Variable introduced
1816+ :version 5.6.11-60.3: Variable introduced
1817 :cli: Yes
1818 :conf: Yes
1819 :scope: Global
1820
1821=== modified file 'doc/source/management/enforce_engine.rst'
1822--- doc/source/management/enforce_engine.rst 2012-12-14 09:58:23 +0000
1823+++ doc/source/management/enforce_engine.rst 2013-06-03 10:03:31 +0000
1824@@ -13,7 +13,7 @@
1825 Version Specific Information
1826 ============================
1827
1828- * :rn:`5.5.24-26.0`
1829+ * :rn:`5.6.11-60.3`
1830 Variable :variable:`enforce_storage_engine` implemented.
1831
1832 System Variables
1833
1834=== modified file 'doc/source/management/expanded_program_option_modifiers.rst'
1835--- doc/source/management/expanded_program_option_modifiers.rst 2012-09-04 23:24:39 +0000
1836+++ doc/source/management/expanded_program_option_modifiers.rst 2013-06-03 10:03:31 +0000
1837@@ -31,7 +31,7 @@
1838 Version Specific Information
1839 ============================
1840
1841- * :rn:`5.5.27-28.0`
1842+ * :rn:`5.6.11-60.3`
1843 Expanded program option modifiers implemented
1844
1845 Examples
1846
1847=== modified file 'doc/source/management/innodb_fake_changes.rst'
1848--- doc/source/management/innodb_fake_changes.rst 2013-05-27 13:59:13 +0000
1849+++ doc/source/management/innodb_fake_changes.rst 2013-06-03 10:03:31 +0000
1850@@ -4,7 +4,7 @@
1851 Support for Fake Changes
1852 ==========================
1853
1854-Restarting a slave server in a replication environment or setting up new slave server can cause a replication reads slower. This is happening because replication in |MySQL| is single-threaded and because it needs to read the data before it can execute the queries. The process can be speeded up by having prefetch threads to warm the server: replay statements and then rollback at commit.
1855+Restarting a slave server in a replication environment or setting up new slave server can cause a replication reads slower. This is happening because replication in |MySQL| is single-threaded and because it needs to read the data before it can execute the queries. The process can be sped up by having prefetch threads to warm the server: replay statements and then rollback at commit.
1856
1857 That makes prefetch simple but has high overhead from locking rows only to undo changes at rollback.
1858
1859@@ -35,7 +35,7 @@
1860
1861 .. variable:: innodb_fake_changes
1862
1863- :version 5.5.16-22.0: Introduced
1864+ :version 5.6.11-60.3: Introduced
1865 :scope: ``GLOBAL``
1866 :type: ``BOOLEAN``
1867 :dyn: ``YES``
1868@@ -43,6 +43,16 @@
1869
1870 This variable enables the *Fake Changes* feature.
1871
1872+.. variable:: innodb_locking_fake_changes
1873+
1874+ :version 5.6.11-60.3: Introduced
1875+ :scope: ``GLOBAL``
1876+ :type: ``BOOLEAN``
1877+ :dyn: ``YES``
1878+ :default: ``TRUE``
1879+
1880+ When this variable is set to ``FALSE``, it makes fake transactions not to take any row locks. This feature was implemented because, although fake change transactions downgrade the requested exclusive (X) row locks to shared (S) locks, these S locks prevent X locks from being taken and block the real changes. However, this option is not safe to set to FALSE by default, because the fake changes implementation is not ready for lock-less operation for all workloads. Namely, if a real transaction will remove a row that a fake transaction is doing a secondary index maintenance for, the latter will fail. This option is considered experimental and might be removed in the future if lockless operation mode fixes are implemented.
1881+
1882 Implementation Details
1883 ======================
1884
1885
1886=== removed file 'doc/source/management/innodb_fast_index_creation.rst'
1887--- doc/source/management/innodb_fast_index_creation.rst 2012-12-14 09:58:23 +0000
1888+++ doc/source/management/innodb_fast_index_creation.rst 1970-01-01 00:00:00 +0000
1889@@ -1,63 +0,0 @@
1890-.. _innodb_fast_index_creation:
1891-
1892-=====================
1893- Fast Index Creation
1894-=====================
1895-
1896-Percona has implemented several changes related to |MySQL|'s fast index creation feature. Extended features, besides disabling :variable:`fast_index_creation`, can be enabled with :variable:`expand_fast_index_creation`.
1897-
1898-Disabling Fast Index Creation
1899-=============================
1900-
1901-Fast index creation was implemented in |MySQL| as a way to speed up the process of adding or dropping indexes on tables with many rows. However, cases have been found in which fast index creation creates an inconsistency between |MySQL| and |InnoDB| data dictionaries.
1902-
1903-This feature implements a session variable that disables fast index creation. This causes indexes to be created in the way they were created before fast index creation was implemented. While this is slower, it avoids the problem of data dictionary inconsistency between |MySQL| and |InnoDB|.
1904-
1905-
1906-Tunable buffer size for fast index creation
1907-===========================================
1908-
1909-|Percona Server| supports tunable buffer size for fast index creation in |InnoDB|. This value was calculated based on the merge block size (which was hardcoded to 1 MB) and the minimum index record size. By adding the session variable :variable:`innodb_merge_sort_block_size` block size that is used in the merge sort can now be adjusted for better performance.
1910-
1911-
1912-Version Specific Information
1913-============================
1914-
1915- * :rn:`5.5.8-20.0`:
1916- Variable :variable:`fast_index_creation` implemented.
1917-
1918- * :rn:`5.5.11-20.2`:
1919- Expanded the applicability of fast index creation to :command:`mysqldump`, ``ALTER TABLE``, and ``OPTIMIZE TABLE``.
1920-
1921- * :rn:`5.5.27-28.0`
1922- Variable :variable:`innodb_merge_sort_block_size` implemented.
1923-
1924-System Variables
1925-================
1926-
1927-.. variable:: fast_index_creation
1928-
1929- :cli: Yes
1930- :conf: No
1931- :scope: Local
1932- :dyn: Yes
1933- :vartype: Boolean
1934- :default: ON
1935- :range: ON/OFF
1936-
1937-.. variable:: innodb_merge_sort_block_size
1938-
1939- :cli: Yes
1940- :conf: Yes
1941- :scope: Global
1942- :dyn: Yes
1943- :vartype: ULONG
1944- :default: 1048576 (1M)
1945- :range: 1048576 - 1073741824 (1G)
1946-
1947-Other Reading
1948-=============
1949-
1950- * `Thinking about running OPTIMIZE on your InnoDB Table? Stop! <http://www.mysqlperformanceblog.com/2010/12/09/thinking-about-running-optimize-on-your-innodb-table-stop/>`_
1951-
1952- * `Building Indexes by Sorting In Innodb <http://www.mysqlperformanceblog.com/2012/06/19/building-indexes-by-sorting-in-innodb-aka-fast-index-creation/>`_
1953
1954=== modified file 'doc/source/management/innodb_kill_idle_trx.rst'
1955--- doc/source/management/innodb_kill_idle_trx.rst 2013-05-26 13:51:37 +0000
1956+++ doc/source/management/innodb_kill_idle_trx.rst 2013-06-03 10:03:31 +0000
1957@@ -11,7 +11,7 @@
1958
1959 .. variable:: innodb_kill_idle_transaction
1960
1961- :version 5.5.16-22.0: Introduced
1962+ :version 5.6.11-60.3: Introduced
1963 :scope: ``GLOBAL``
1964 :config: ``YES``
1965 :dyn: ``YES``
1966
1967=== modified file 'doc/source/management/pam_plugin.rst'
1968--- doc/source/management/pam_plugin.rst 2013-02-06 10:26:45 +0000
1969+++ doc/source/management/pam_plugin.rst 2013-06-03 10:03:31 +0000
1970@@ -68,5 +68,5 @@
1971 Version Specific Information
1972 ============================
1973
1974- * :rn:`5.5.24-26.0`
1975+ * :rn:`5.6.11-60.3`
1976 PAM authentication plugin has been integrated with |Percona Server|.
1977
1978=== modified file 'doc/source/management/secure_file_priv_extended.rst'
1979--- doc/source/management/secure_file_priv_extended.rst 2012-09-04 23:24:39 +0000
1980+++ doc/source/management/secure_file_priv_extended.rst 2013-06-03 10:03:31 +0000
1981@@ -10,7 +10,7 @@
1982 Version Specific Information
1983 ============================
1984
1985- * :rn:`5.5.25a-27.1`
1986+ * :rn:`5.6.11-60.3`
1987 Variable :variable:`secure-file-priv` extended behavior implemented.
1988
1989 System Variables
1990
1991=== removed file 'doc/source/management/udf_maatkit.rst'
1992--- doc/source/management/udf_maatkit.rst 2013-05-10 09:39:17 +0000
1993+++ doc/source/management/udf_maatkit.rst 1970-01-01 00:00:00 +0000
1994@@ -1,49 +0,0 @@
1995-.. _udf_maatkit:
1996-
1997-======================================
1998- *Percona Toolkit* and *Maatkit* UDFs
1999-======================================
2000-
2001-Three *Percona Toolkit* and *Maatkit* UDFs that provide faster checksums are provided:
2002-
2003- * ``fnv_udf``
2004-
2005- * ``fnv1a_udf``
2006-
2007- * ``murmur_udf``
2008-
2009-Version Specific Information
2010-============================
2011-
2012- * 5.1.53-12.4:
2013- Began distributing ``fnv_udf``, ``fnv1a_udf``, and ``murmur_udf``.
2014-
2015-Other Information
2016-=================
2017-
2018- * Author / Origin:
2019- Baron Schwartz
2020-
2021-Installation
2022-============
2023-
2024-Use of the Percona Software Repositories simplifies the installation of *Percona Toolkit*. Once the repository has been set up on your system, *Percona Toolkit* can be installed by executing: ::
2025-
2026- $ yum install percona-toolkit
2027-
2028-This will place the *Percona Toolkit* UDFs onto your system. However, they will not yet be installed into the |MySQL| server. To install one of the UDF``s into the server, execute one of the following commands, depending on which UDF you want to install: ::
2029-
2030- $ mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME ``fnv_udf.so``"
2031- $ mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME ``fnv1a_udf.so``"
2032- $ mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME ``murmur_udf.so``"
2033-
2034-Executing each of these commands will install its respective UDF into the server.
2035-
2036-If you have any difficulty, or require more detailed information, refer to the *Maatkit* `Installing UDFs <http://code.google.com/p/maatkit/wiki/InstallingUdfs>`_ documentation.
2037-
2038-
2039-Other Reading
2040-=============
2041-
2042- * *Percona Toolkit* - http://www.percona.com/doc/percona-toolkit
2043- * *Maatkit* - http://www.maatkit.org/
2044
2045=== added file 'doc/source/management/udf_percona_toolkit.rst'
2046--- doc/source/management/udf_percona_toolkit.rst 1970-01-01 00:00:00 +0000
2047+++ doc/source/management/udf_percona_toolkit.rst 2013-06-03 10:03:31 +0000
2048@@ -0,0 +1,54 @@
2049+.. _udf_percona_toolkit:
2050+
2051+========================
2052+ *Percona Toolkit* UDFs
2053+========================
2054+
2055+Three *Percona Toolkit* UDFs that provide faster checksums are provided:
2056+
2057+ * ``fnv_udf``
2058+
2059+ * ``fnv1a_udf``
2060+
2061+ * ``murmur_udf``
2062+
2063+Version Specific Information
2064+============================
2065+
2066+ * :rn:`5.6.11-60.3`:
2067+ Began distributing ``fnv_udf``, ``fnv1a_udf``, and ``murmur_udf``.
2068+
2069+Other Information
2070+=================
2071+
2072+ * Author / Origin:
2073+ Baron Schwartz
2074+
2075+Installation
2076+============
2077+
2078+Use of the Percona Software Repositories simplifies the installation of *Percona Toolkit*. Once the repository has been set up on your system, *Percona Toolkit* can be installed by executing: ::
2079+
2080+ $ yum install percona-toolkit
2081+
2082+This will place the *Percona Toolkit* UDFs onto your system. However, they will not yet be installed into the |MySQL| server. To install one of the UDF``s into the server, execute one of the following commands, depending on which UDF you want to install: ::
2083+
2084+ $ mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME ``fnv_udf.so``"
2085+ $ mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME ``fnv1a_udf.so``"
2086+ $ mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME ``murmur_udf.so``"
2087+
2088+Executing each of these commands will install its respective UDF into the server.
2089+
2090+Troubleshooting
2091+================
2092+
2093+If you get the error: ::
2094+
2095+ ERROR 1126 (HY000): Can't open shared library 'fnv_udf.so' (errno: 22 fnv_udf.so: cannot open shared object file: No such file or directory)
2096+
2097+Then you may need to copy the .so file to another location in your system. Try both ``/lib`` and ``/usr/lib``. Look at your environment's ``$LD_LIBRARY_PATH`` variable for clues. If none is set, and neither ``/lib`` nor ``/usr/lib`` works, you may need to set ``LD_LIBRARY_PATH`` to ``/lib`` or ``/usr/lib``.
2098+
2099+Other Reading
2100+=============
2101+
2102+ * *Percona Toolkit* `documentation <http://www.percona.com/doc/percona-toolkit/>`_
2103
2104=== modified file 'doc/source/management/utility_user.rst'
2105--- doc/source/management/utility_user.rst 2012-09-04 23:24:39 +0000
2106+++ doc/source/management/utility_user.rst 2013-06-03 10:03:31 +0000
2107@@ -26,7 +26,7 @@
2108
2109 In order to have the ability for a special type of MySQL user, which will have a very limited and special amount of control over the system and can not be see or modified by any other user including the root user, three new options have been added.
2110
2111-Option :variable:`utility_user` specifies the user which the system will create and recognize as the utility user. The host in the utility user specification follows conventions described in the `MySQL manual <http://dev.mysql.com/doc/refman/5.5/en/connection-access.html>`_, i.e. it allows wildcards and IP masks. Anonymous user names are not permitted to be used for the utility user name.
2112+Option :variable:`utility_user` specifies the user which the system will create and recognize as the utility user. The host in the utility user specification follows conventions described in the `MySQL manual <http://dev.mysql.com/doc/refman/5.6/en/connection-access.html>`_, i.e. it allows wildcards and IP masks. Anonymous user names are not permitted to be used for the utility user name.
2113
2114 This user must not be an exact match to any other user that exists in the mysql.user table. If the server detects that the user specified with this option exactly matches any user within the mysql.user table on start up, the server will report an error and shut down gracefully. If host name wildcards are used and a more specific user specification is identified on start up, the server will report a warning and continue.
2115
2116@@ -51,7 +51,7 @@
2117
2118 .. variable:: utility_user
2119
2120- :version 5.5.27-28.0: Implemented
2121+ :version 5.6.11-60.3: Implemented
2122 :cli: Yes
2123 :conf: utility_user=<user@host>
2124 :scope: Global
2125@@ -63,7 +63,7 @@
2126
2127 .. variable:: utility_user_password
2128
2129- :version 5.5.27-28.0: Implemented
2130+ :version 5.6.11-60.3: Implemented
2131 :cli: Yes
2132 :conf: utility_user_password=<password>
2133 :scope: Global
2134@@ -75,7 +75,7 @@
2135
2136 .. variable:: utility_user_schema_access
2137
2138- :version 5.5.27-28.0: Implemented
2139+ :version 5.6.11-60.3: Implemented
2140 :cli: Yes
2141 :conf: utility_user_schema_access=<schema>,<schema>,<schema>
2142 :scope: Global
2143
2144=== modified file 'doc/source/performance/innodb_numa_support.rst'
2145--- doc/source/performance/innodb_numa_support.rst 2013-05-12 09:13:00 +0000
2146+++ doc/source/performance/innodb_numa_support.rst 2013-06-03 10:03:31 +0000
2147@@ -13,7 +13,7 @@
2148 Version Specific Information
2149 ============================
2150
2151- * :rn:`5.5.28-29.1`
2152+ * :rn:`5.6.11-60.3`
2153 Improved ``NUMA`` support implemented. This feature was ported from Twitter's |MySQL| patches.
2154
2155 System Variables
2156
2157=== modified file 'doc/source/performance/query_cache_enhance.rst'
2158--- doc/source/performance/query_cache_enhance.rst 2013-05-26 07:09:29 +0000
2159+++ doc/source/performance/query_cache_enhance.rst 2013-06-03 10:03:31 +0000
2160@@ -38,19 +38,19 @@
2161
2162 This features provides a new thread state - ``Waiting on query cache mutex``. It has always been difficult to spot query cache bottlenecks because these bottlenecks usually happen intermittently and are not directly reported by the server. This new thread state appear in the output of SHOW PROCESSLIST, easing diagnostics.
2163
2164-Imagine that we run three queries simultaneously (each one in a separate thread):
2165-
2166- > SELECT number from t where id > 0;
2167- > SELECT number from t where id > 0;
2168- > SELECT number from t where id > 0;
2169-
2170-If we experience query cache contention, the output of SHOW PROCESSLIT will look like this: ::
2171+Imagine that we run three queries simultaneously (each one in a separate thread): ::
2172+
2173+ > SELECT number from t where id > 0;
2174+ > SELECT number from t where id > 0;
2175+ > SELECT number from t where id > 0;
2176+
2177+If we experience query cache contention, the output of ``SHOW PROCESSLIST`` will look like this: ::
2178
2179 > SHOW PROCESSLIST;
2180 Id User Host db Command Time State Info
2181 2 root localhost test Sleep 2 NULL
2182 3 root localhost test Query 2 Waiting on query cache mutex SELECT number from t where id > 0;
2183- 4 root localhost test Query 1 Waiting on query cache mutex SELECT number from t where id > 0;
2184+ 4 root localhost test Query 1 Waiting on query cache mutex SELECT number from t where id > 0;
2185 5 root localhost test Query 0 NULL
2186
2187 Ignoring comments
2188@@ -66,36 +66,6 @@
2189 If the option is enabled, the queries are considered identical, so the server will execute and cache the first one and will serve the second one directly from the query cache.
2190
2191
2192-.. Version Specific Information
2193-.. ----------------------------
2194-
2195-.. Disabling the query cache completely
2196-
2197-.. Percona Server Version Comments
2198-.. 5.1.49-12.0 Full functionality available.
2199-.. Diagnosing contention more easily
2200-
2201-.. Percona Server Version Comments
2202-.. 5.1.49-12.0 Full functionality available.
2203-.. Ignoring comments
2204-
2205-.. Percona Server Version Comments
2206-.. 5.1.47-11.0 Critical bug (see MySQL bug 55032). Release was recalled.
2207-.. 5.1.47-11.1 Fixed critical bug from previous release. MySQL bug 55032 actual. Bug b603618 actual. Bug 603619 actual.
2208-.. 5.1.47-11.2 Full functionality available.
2209-.. 5.1.48-12.0 Full functionality available.
2210-
2211-.. Other Information
2212-
2213-.. Disabling the query cache completely
2214-
2215-.. Author/Origin Percona
2216-.. Bugs fixed LP bug 609027, MySQL bug 38551
2217-.. Diagnosing contention more easily
2218-
2219-.. Author/Origin Percona
2220-.. Bugs fixed LP bug589484
2221-
2222 System Variables
2223 ================
2224
2225@@ -116,8 +86,4 @@
2226
2227 * `MySQL general thread states <http://dev.mysql.com/doc/refman/5.1/en/general-thread-states.html>`_
2228
2229- * `RAII <http://en.wikibooks.org/wiki/More_C%2B%2B_Idioms/Resource_Acquisition_Is_Initialization>`_
2230-
2231- * `Scope guard <http://en.wikibooks.org/wiki/More_C%2B%2B_Idioms/Scope_Guard>`_
2232-
2233 * `Query cache freezes <http://www.mysqlperformanceblog.com/2009/03/19/mysql-random-freezes-could-be-the-query-cache/>`_
2234
2235=== modified file 'doc/source/reliability/error_pad.rst'
2236--- doc/source/reliability/error_pad.rst 2013-05-27 13:59:13 +0000
2237+++ doc/source/reliability/error_pad.rst 2013-06-03 10:03:31 +0000
2238@@ -4,17 +4,17 @@
2239 Error Code Compatibility
2240 ==========================
2241
2242-|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.
2243+|Percona Server| with |XtraDB| has error code incompatibilities with |MySQL| 5.6. 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.
2244
2245 The reasons for the current incompatibilities are:
2246
2247- * |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.
2248+ * |Percona Server| with |XtraDB| contains features that have been backported from MyQL 5.6. Some of the |MySQL| 5.6 features added new error codes.
2249
2250 * Some |Percona Server| with |XtraDB| features have added new error codes.
2251
2252-The 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.
2253+The solution to the first problem is to preserve |MySQL| 5.6 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.6.
2254
2255-After migrating |Percona Server| / |XtraDB| to |MySQL| 5.5, users might experience troubles because of this.
2256+After migrating |Percona Server| / |XtraDB| to |MySQL| 5.6, users might experience troubles because of this.
2257
2258 The 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.
2259
2260@@ -51,5 +51,5 @@
2261 Version-Specific Information
2262 ============================
2263
2264- * 5.5.8-20.0
2265- Full functionality available.
2266+ * :rn:`5.6.11-60.3`
2267+ Feature ported from |Percona Server| 5.5.
2268
2269=== modified file 'doc/source/reliability/log_connection_error.rst'
2270--- doc/source/reliability/log_connection_error.rst 2013-05-27 13:59:13 +0000
2271+++ doc/source/reliability/log_connection_error.rst 2013-06-03 10:03:31 +0000
2272@@ -10,5 +10,5 @@
2273 Version-Specific Information
2274 ============================
2275
2276- * 5.5.8-20.0:
2277- Full functionality available.
2278+ * :rn:`5.6.11-30.3`:
2279+ Feature ported from |Percona Server| 5.5.
2280
2281=== modified file 'doc/source/reliability/show_slave_status_nolock.rst'
2282--- doc/source/reliability/show_slave_status_nolock.rst 2013-05-06 15:43:51 +0000
2283+++ doc/source/reliability/show_slave_status_nolock.rst 2013-06-03 10:03:31 +0000
2284@@ -14,10 +14,12 @@
2285
2286 This will display the slave's status as if there were no lock, allowing the user to detect and understand the situation that is occurring.
2287
2288-**NOTE:** The information given when ``NOLOCK`` is used may be slightly inconsistent with the actual situation while the lock is being held.
2289+.. note::
2290+
2291+ The information given when ``NOLOCK`` is used may be slightly inconsistent with the actual situation while the lock is being held.
2292
2293
2294 Version Specific Information
2295 ============================
2296
2297- * 5.5.8-20.0:
2298+ * :rn:`5.6.11-60.3`: Feature ported from |Percona Server| 5.5.
2299
2300=== added file 'doc/source/scalability/innodb_io.rst'
2301--- doc/source/scalability/innodb_io.rst 1970-01-01 00:00:00 +0000
2302+++ doc/source/scalability/innodb_io.rst 2013-06-03 10:03:31 +0000
2303@@ -0,0 +1,71 @@
2304+.. _innodb_io_page:
2305+
2306+===================================
2307+ Improved |InnoDB| I/O Scalability
2308+===================================
2309+
2310+Because |InnoDB| is a complex storage engine it must be configured properly in order to perform at its best. Some points are not configurable in standard |InnoDB|. The goal of this feature is to provide a more exhaustive set of options for |XtraDB|, like ability to change the log block size.
2311+
2312+Version Specific Information
2313+============================
2314+
2315+ * :rn:`5.6.11-60.3`
2316+
2317+ * Feature ported from |Percona Server| 5.5
2318+
2319+System Variables
2320+================
2321+
2322+
2323+.. variable:: innodb_use_global_flush_log_at_trx_commit
2324+
2325+ :cli: Yes
2326+ :conf: Yes
2327+ :scope: Global
2328+ :dyn: Yes
2329+ :type: Boolean
2330+ :default: True
2331+ :range: True/False
2332+
2333+This variable is used to control the ability of the user to set the value of the global |MySQL| variable ``innodb_flush_log_at_trx_commit``.
2334+
2335+If ``innodb_use_global_flush_log_at_trx_commit=0`` (False), the client can set the global |MySQL| variable, using: ::
2336+
2337+ SET innodb_use_global_flush_log_at_trx_commit=N
2338+
2339+If ``innodb_use_global_flush_log_at_trx_commit=1`` (True), the user session will use the current value of ``innodb_flush_log_at_trx_commit``, and the user cannot reset the value of the global variable using a ``SET`` command.
2340+
2341+.. variable:: innodb_log_block_size
2342+
2343+ :cli: Yes
2344+ :conf: Yes
2345+ :scope: Global
2346+ :dyn: No
2347+ :vartype: Numeric
2348+ :default: 512
2349+ :units: Bytes
2350+
2351+This variable changes the size of transaction log records. The default size of 512 bytes is good in most situations. However, setting it to 4096 may be a good optimization with SSD cards. While settings other than 512 and 4096 are possible, as a practical matter these are really the only two that it makes sense to use. Clean restart and removal of the old logs is needed for the variable :variable:`innodb_log_block_size` to be changed.
2352+
2353+Status Variables
2354+----------------
2355+
2356+The following information has been added to ``SHOW ENGINE INNODB STATUS`` to confirm the checkpointing activity: ::
2357+
2358+ The max checkpoint age
2359+ The current checkpoint age target
2360+ The current age of the oldest page modification which has not been flushed to disk yet.
2361+ The current age of the last checkpoint
2362+ ...
2363+ ---
2364+ LOG
2365+ ---
2366+ Log sequence number 0 1059494372
2367+ Log flushed up to 0 1059494372
2368+ Last checkpoint at 0 1055251010
2369+ Max checkpoint age 162361775
2370+ Checkpoint age target 104630090
2371+ Modified age 4092465
2372+ Checkpoint age 4243362
2373+ 0 pending log writes, 0 pending chkp writes
2374+ ...

Subscribers

People subscribed via source and target branches