Merge lp:~hrvojem/percona-server/bug1057031-5.1 into lp:percona-server/5.1

Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Stewart Smith
Approved revision: 500
Merged at revision: 508
Proposed branch: lp:~hrvojem/percona-server/bug1057031-5.1
Merge into: lp:percona-server/5.1
Diff against target: 753 lines (+55/-181)
36 files modified
doc/source/development.rst (+4/-4)
doc/source/diagnostics/innodb_deadlock_count.rst (+1/-1)
doc/source/diagnostics/mysql_syslog.rst (+1/-1)
doc/source/diagnostics/process_list.rst (+0/-25)
doc/source/diagnostics/response_time_distribution.rst (+3/-3)
doc/source/diagnostics/show_engines.rst (+1/-1)
doc/source/diagnostics/slow_extended.rst (+2/-14)
doc/source/flexibility/buff_read_ahead_area.rst (+1/-1)
doc/source/flexibility/innodb_fast_shutdown.rst (+1/-1)
doc/source/flexibility/log_warnings_suppress.rst (+3/-33)
doc/source/flexibility/mysql_remove_eol_carret.rst (+1/-1)
doc/source/flexibility/mysqlbinlog_change_db.rst (+1/-1)
doc/source/flexibility/replication_skip_single_statement.rst (+1/-1)
doc/source/index.rst (+1/-2)
doc/source/installation.rst (+1/-1)
doc/source/management/changed_page_tracking.rst (+1/-1)
doc/source/management/innodb_buffer_pool_shm.rst (+3/-3)
doc/source/management/innodb_expand_import.rst (+3/-22)
doc/source/management/innodb_extended_fast_index_creation.rst (+1/-1)
doc/source/management/innodb_fast_index_creation.rst (+2/-2)
doc/source/management/innodb_fast_index_renaming.rst (+0/-38)
doc/source/management/innodb_lru_dump_restore.rst (+1/-1)
doc/source/management/sql_no_fcache.rst (+1/-1)
doc/source/management/udf_maatkit.rst (+1/-1)
doc/source/performance/handlersocket.rst (+1/-1)
doc/source/performance/innodb_doublewrite_path.rst (+3/-3)
doc/source/performance/innodb_lazy_drop_table.rst (+3/-3)
doc/source/performance/innodb_purge_thread.rst (+2/-2)
doc/source/performance/remove_fcntl_excessive_calls.rst (+1/-1)
doc/source/release-notes/Percona-Server-5.1.50-rel12.1.rst (+1/-1)
doc/source/reliability/crash_resistant_replication.rst (+1/-1)
doc/source/reliability/error_pad.rst (+1/-1)
doc/source/reliability/log_connection_error.rst (+1/-1)
doc/source/reliability/show_slave_status_nolock.rst (+1/-2)
doc/source/scalability/innodb_extra_rseg.rst (+3/-3)
doc/source/scalability/innodb_io.rst (+2/-2)
To merge this branch: bzr merge lp:~hrvojem/percona-server/bug1057031-5.1
Reviewer Review Type Date Requested Status
Stewart Smith (community) Approve
Review via email: mp+139694@code.launchpad.net
To post a comment you must log in.
Stewart Smith (stewart) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/source/development.rst'
2--- doc/source/development.rst 2012-01-27 11:37:42 +0000
3+++ doc/source/development.rst 2012-12-13 13:30:28 +0000
4@@ -19,7 +19,7 @@
5
6 Overview
7 ~~~~~~~~
8-At Percona we use `Bazaar <http://www.bazaar-vcs.org>`_ for source
9+At Percona we use `Bazaar <http://bazaar.canonical.com/en/>`_ for source
10 control and `launchpad <http://www.launchpad.net>`_ for both
11 code hosting and release management.
12
13@@ -205,7 +205,7 @@
14 Percona Xtrabackup
15 ~~~~~~~~~~~~~~~~~~
16
17-`<http://jenkins.percona.com/view/Percona%20Xtrabackup/>`_
18+`<http://jenkins.percona.com/view/XtraBackup/>`_
19
20 We currently build both xtrabackup 1.6 and xtrabackup trunk (will become 1.7).
21
22@@ -221,14 +221,14 @@
23 Percona Server 5.1
24 ------------------
25
26-`<http://jenkins.percona.com/view/Percona%20Server%205.1/>`_
27+`<http://jenkins.percona.com/view/PS%205.1/>`_
28
29 We have trunk and param jobs. We also have a valgrind job that will run after a successful trunk build.
30
31 Percona Server 5.5
32 ------------------
33
34-`<http://jenkins.percona.com/view/Percona%20Server%205.5/>`_
35+`<http://jenkins.percona.com/view/PS%205.5/>`_
36
37 Similar to 5.1, but for PS5.5 instead.
38
39
40=== modified file 'doc/source/diagnostics/innodb_deadlock_count.rst'
41--- doc/source/diagnostics/innodb_deadlock_count.rst 2011-10-07 00:55:06 +0000
42+++ doc/source/diagnostics/innodb_deadlock_count.rst 2012-12-13 13:30:28 +0000
43@@ -36,7 +36,7 @@
44 Version Specific Information
45 ============================
46
47- * 5.1.47-11.0:
48+ * :rn:`5.1.47-rel11.1`:
49 Full functionality available.
50
51 Status Variables
52
53=== modified file 'doc/source/diagnostics/mysql_syslog.rst'
54--- doc/source/diagnostics/mysql_syslog.rst 2012-05-29 18:31:23 +0000
55+++ doc/source/diagnostics/mysql_syslog.rst 2012-12-13 13:30:28 +0000
56@@ -10,7 +10,7 @@
57 Version Specific Information
58 ============================
59
60- * 5.1.49-12.0:
61+ * :rn:`5.1.49-rel12.0`:
62 Full functionality available.
63
64 Other Information
65
66=== modified file 'doc/source/diagnostics/process_list.rst'
67--- doc/source/diagnostics/process_list.rst 2011-10-07 00:55:06 +0000
68+++ doc/source/diagnostics/process_list.rst 2012-12-13 13:30:28 +0000
69@@ -6,29 +6,6 @@
70
71 This page describes Percona changes to both the standard |MySQL| ``SHOW PROCESSLIST`` command and the standard |MySQL| ``INFORMATION_SCHEMA`` table ``PROCESSLIST``.
72
73-The changes that have been made as of version 5.5 of the server are:
74-
75- * ``SHOW PROCESSLIST`` command:
76-
77- * added columns ``ROWS_EXAMINED``, ``ROWS_SENT``, and ``ROWS_READ``
78-
79- * ``PROCESSLIST`` table:
80-
81- * added columns ``TIME_MS``, ``ROWS_EXAMINED``, ``ROWS_SENT``, and ``ROWS_READ``
82-
83-Version Specific Information
84-============================
85-
86- * 5.0.91-22:
87-
88- * Added column ``TIME_MS`` to table ``PROCESSLIST``.
89-
90- * 5.5.10-20.1:
91-
92- * Added columns ``ROWS_EXAMINED``, ``ROWS_SENT``, and ``ROWS_READ`` to ``SHOW PROCESSLIST`` command.
93-
94- * Added columns ``ROWS_EXAMINED``, ``ROWS_SENT``, and ``ROWS_READ`` to table ``PROCESSLIST``.
95-
96 INFORMATION_SCHEMA Tables
97 =========================
98
99@@ -48,8 +25,6 @@
100 :column ROWS_EXAMINED: The number of rows examined by the statement being executed.
101 :column ROWS_SENT: The number of rows sent by the statement being executed.
102 :column ROWS_READ: The number of rows read by the statement being executed.
103- :version 5.0.91-22: Added column ``TIME_MS``
104- :version 5.5.10-20.1: Added columns ``ROWS_EXAMINED``, ``ROWS_SENT``, and ``ROWS_READ``
105
106
107 Example Output
108
109=== modified file 'doc/source/diagnostics/response_time_distribution.rst'
110--- doc/source/diagnostics/response_time_distribution.rst 2012-12-10 14:01:11 +0000
111+++ doc/source/diagnostics/response_time_distribution.rst 2012-12-13 13:30:28 +0000
112@@ -193,10 +193,10 @@
113 Version Specific Information
114 ============================
115
116- * 5.1.49-12.0:
117+ * :rn:`5.1.49-rel12.0`:
118 Full functionality available.
119
120- * 5.1.53-12.4:
121+ * :rn:`5.1.53-12.4`:
122 Introduced :variable:`have_response_time_distribution`.
123
124 System Variables
125@@ -232,7 +232,7 @@
126
127 .. variable:: enable_query_response_time_stats
128
129- :version 5.1.49-12.0: Introduced.
130+ :version 5.1.49-rel12.0: Introduced.
131 :cli: Yes
132 :conf: Yes
133 :scope: Global
134
135=== modified file 'doc/source/diagnostics/show_engines.rst'
136--- doc/source/diagnostics/show_engines.rst 2011-10-07 00:55:06 +0000
137+++ doc/source/diagnostics/show_engines.rst 2012-12-13 13:30:28 +0000
138@@ -29,7 +29,7 @@
139 Version-Specific Information
140 ============================
141
142- * 5.1.49-12.0:
143+ * :rn:`5.1.49-rel12.0`:
144 Full functionality available.
145
146 Other Information
147
148=== modified file 'doc/source/diagnostics/slow_extended.rst'
149--- doc/source/diagnostics/slow_extended.rst 2012-09-17 07:36:57 +0000
150+++ doc/source/diagnostics/slow_extended.rst 2012-12-13 13:30:28 +0000
151@@ -8,20 +8,12 @@
152
153 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|.
154
155-You can use *Percona Toolkit* 's ''mk-query-digest'' tool to aggregate similar queries together and report on those that consume the most execution time.
156+You can use *Percona Toolkit*'s ''pt-query-digest'' tool to aggregate similar queries together and report on those that consume the most execution time.
157
158
159 Version Specific Information
160 ============================
161
162- * ``4.1.x``:
163-
164- * Limited functionality available: only microsecond resolution, no added statistics.
165-
166- * ``5.0.x``:
167-
168- * Full functionality available.
169-
170 * ``5.1.x``:
171
172 * Microsecond resolution included in official |MySQL| server; this feature adds statistics.
173@@ -34,7 +26,7 @@
174
175 * Full functionality of :variable:`use_global_log_slow_control` available.
176
177- * Fixed :bug:`600684` - :variable:`log_slow_verbosity` ``=iInnodb`` doesn't work on slave (statement-based replication)
178+ * Fixed :bug:`600684` - :variable:`log_slow_verbosity` ``=Innodb`` doesn't work on slave (statement-based replication)
179
180 * :rn:`5.1.53-11.7`:
181
182@@ -134,16 +126,12 @@
183
184 If ``TRUE``, a timestamp is printed on every slow log record. Multiple records may have the same time.
185
186-**NOTE:** This variable has been renamed to :variable:`slow_query_log_timestamp_always` since :rn:`5.5.10-20.1`.
187-
188-
189 .. variable:: log_slow_verbosity
190
191 :cli: Yes
192 :conf: Yes
193 :scope: Global, session
194 :dyn: Yes
195- :version 5.5.8-20.0: Added ``profiling`` and ``profiling_use_getrusage``
196
197 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:
198
199
200=== modified file 'doc/source/flexibility/buff_read_ahead_area.rst'
201--- doc/source/flexibility/buff_read_ahead_area.rst 2012-06-13 10:52:23 +0000
202+++ doc/source/flexibility/buff_read_ahead_area.rst 2012-12-13 13:30:28 +0000
203@@ -18,7 +18,7 @@
204 Version Specific Information
205 ============================
206
207- * :rn:`5.1.47-12.0` :
208+ * :rn:`5.1.49-rel12.0` :
209 Full functionality available.
210
211 Other Information
212
213=== modified file 'doc/source/flexibility/innodb_fast_shutdown.rst'
214--- doc/source/flexibility/innodb_fast_shutdown.rst 2011-10-07 00:55:06 +0000
215+++ doc/source/flexibility/innodb_fast_shutdown.rst 2012-12-13 13:30:28 +0000
216@@ -15,7 +15,7 @@
217 Version Specific Information
218 ============================
219
220- * 5.1.52-12.3:
221+ * :rn:`5.1.52-12.3`
222 Full functionality available.
223
224 Other Information
225
226=== modified file 'doc/source/flexibility/log_warnings_suppress.rst'
227--- doc/source/flexibility/log_warnings_suppress.rst 2011-10-07 00:55:06 +0000
228+++ doc/source/flexibility/log_warnings_suppress.rst 2012-12-13 13:30:28 +0000
229@@ -10,22 +10,15 @@
230 Version Specific Information
231 ============================
232
233- * 5.1.47-11.0:
234+ * :rn:`5.1.47-rel11.1`
235 System variable :variable:`suppress_log_warning_1592` introduced.
236
237- * 5.5.8-20.0:
238- System variable :variable:`suppress_log_warning_1592` replaced by :variable:`log_warnings_silence`.
239-
240- * 5.5.10-20.1:
241- Renamed variable :variable:`log_warnings_silence` to :variable:`log_warnings_suppress`.
242-
243 System Variables
244 ================
245
246 .. variable:: suppress_log_warning_1592
247
248- :version 5.1.47-11.0: Introduced.
249- :version 5.5.8-20.0: Deleted.
250+ :version 5.1.47-rel11.1: Introduced.
251 :cli: Yes
252 :conf: Yes
253 :scope: Global
254@@ -46,33 +39,10 @@
255
256 090213 16:58:54 [Warning] Statement is not safe to log in statement format.
257
258-This variable was obsoleted, beginning in release :rn:`5.5.8-20.0`. It still exists in versions :rn:`5.1.47-11.0` to :rn:`5.1.54-12.5`.
259-
260-.. variable:: log_warnings_suppress
261-
262- :version 5.5.8-20.0: Introduced.
263- :version 5.5.10-20.1: Renamed.
264- :cli: Yes
265- :conf: Yes
266- :scope: Global
267- :dyn: Yes
268- :vartype: SET
269- :default: ``(empty string)``
270- :range: ``(empty string)``, ``1592``
271-
272-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.
273-
274-It is intended to provide a more general mechanism for disabling warnings than existed previously with variable suppress_log_warning_1592.
275-
276-When set to the empty string, no warnings are disabled. When set to ``1592``, warning #1592 messages (unsafe statement for binary logging) are suppressed.
277-
278-In the future, the ability to optionally disable additional warnings may also be added.
279-
280-
281 Related Reading
282 ===============
283
284- * `MySQL bug 42851 <http://bugs.mysql.com/bug.php?id=42851>`_
285+ * `MySQL bug #42851 <http://bugs.mysql.com/bug.php?id=42851>`_
286
287 * `MySQL InnoDB replication <http://dev.mysql.com/doc/refman/5.1/en/innodb-and-mysql-replication.html>`_
288
289
290=== modified file 'doc/source/flexibility/mysql_remove_eol_carret.rst'
291--- doc/source/flexibility/mysql_remove_eol_carret.rst 2011-10-07 00:55:06 +0000
292+++ doc/source/flexibility/mysql_remove_eol_carret.rst 2012-12-13 13:30:28 +0000
293@@ -14,7 +14,7 @@
294 Version Specific Information
295 ============================
296
297- * 5.1.50-12.1:
298+ * :rn:`5.1.50-rel12.1`
299 Full functionality.
300
301 Client Command Line Parameter
302
303=== modified file 'doc/source/flexibility/mysqlbinlog_change_db.rst'
304--- doc/source/flexibility/mysqlbinlog_change_db.rst 2012-05-17 11:21:21 +0000
305+++ doc/source/flexibility/mysqlbinlog_change_db.rst 2012-12-13 13:30:28 +0000
306@@ -66,7 +66,7 @@
307 Version Specific Information
308 ============================
309
310- * 5.1.62-13.3
311+ * :rn:`5.1.62-13.3`
312 Full functionality.
313
314 Client Command Line Parameter
315
316=== modified file 'doc/source/flexibility/replication_skip_single_statement.rst'
317--- doc/source/flexibility/replication_skip_single_statement.rst 2011-10-07 00:55:06 +0000
318+++ doc/source/flexibility/replication_skip_single_statement.rst 2012-12-13 13:30:28 +0000
319@@ -25,7 +25,7 @@
320 Version Specific Information
321 ============================
322
323- * 5.1.49-12.0:
324+ * :rn:`5.1.49-rel12.0`
325 Full functionality released.
326
327 System Variables
328
329=== modified file 'doc/source/index.rst'
330--- doc/source/index.rst 2012-12-10 14:01:11 +0000
331+++ doc/source/index.rst 2012-12-13 13:30:28 +0000
332@@ -103,7 +103,7 @@
333 reliability/log_connection_error
334 reliability/error_pad
335 reliability/innodb_corrupt_table_action
336- reliability/innodb_recovery_update_relay_log
337+ reliability/crash_resistant_replication
338 reliability/show_slave_status_nolock
339
340 Management Improvements
341@@ -120,7 +120,6 @@
342 management/innodb_lru_dump_restore
343 management/innodb_fast_index_creation
344 management/innodb_extended_fast_index_creation
345- management/innodb_fast_index_renaming
346 management/sql_no_fcache
347 management/udf_maatkit
348 management/innodb_fake_changes
349
350=== modified file 'doc/source/installation.rst'
351--- doc/source/installation.rst 2012-01-09 04:30:56 +0000
352+++ doc/source/installation.rst 2012-12-13 13:30:28 +0000
353@@ -170,7 +170,7 @@
354 Installing |Percona Server| from the Bazaar Source Tree
355 ========================================================
356
357-Percona uses the `Bazaar <http://www.bazaar-vcs.org>`_ revision
358+Percona uses the `Bazaar <http://bazaar.canonical.com/en/>`_ revision
359 control system for development. To build the latest Percona Server
360 from the source tree you will need Bazaar installed on your system.
361
362
363=== modified file 'doc/source/management/changed_page_tracking.rst'
364--- doc/source/management/changed_page_tracking.rst 2012-09-03 09:31:43 +0000
365+++ doc/source/management/changed_page_tracking.rst 2012-12-13 13:30:28 +0000
366@@ -35,7 +35,7 @@
367 .. variable:: innodb_track_changed_pages
368
369 :version 5.1.65-14.0: Variable introduced
370- :cli: No
371+ :cli: Yes
372 :conf: Yes
373 :scope: Global
374 :dyn: No
375
376=== modified file 'doc/source/management/innodb_buffer_pool_shm.rst'
377--- doc/source/management/innodb_buffer_pool_shm.rst 2011-10-07 00:55:06 +0000
378+++ doc/source/management/innodb_buffer_pool_shm.rst 2012-12-13 13:30:28 +0000
379@@ -17,12 +17,12 @@
380 Version Specific Information
381 ============================
382
383- * 5.1.49-12.0:
384+ * :rn:`5.1.49-rel12.0`
385 Feature introduced.
386
387- * 5.1.50-12.1:
388+ * :rn:`5.1.50-rel12.1`
389 System variable :variable:`innodb_buffer_pool_shm_checksum` added.
390
391- * 5.1.58-12.9:
392+ * :rn:`5.1.58-12.9`
393 Feature removed, as LRU Dump/Restore is less invasive, more
394 reliable and a better solution.
395
396=== modified file 'doc/source/management/innodb_expand_import.rst'
397--- doc/source/management/innodb_expand_import.rst 2012-06-13 10:52:23 +0000
398+++ doc/source/management/innodb_expand_import.rst 2012-12-13 13:30:28 +0000
399@@ -74,15 +74,15 @@
400 Version Specific Information
401 ============================
402
403- * 5.5.10-20.1:
404- Renamed variable :variable:`innodb_expand_import` to :variable:`innodb_import_table_from_xtrabackup`.
405+ * :rn:`5.1.50-rel12.1`
406+ Introduced variable :variable:`innodb_expand_import`.
407
408 System Variables
409 ================
410
411 .. variable:: innodb_expand_import
412
413- :version 5.5.10-20.1: Renamed.
414+ :version 5.1.50-rel12.1: Introduced
415 :cli: Yes
416 :conf: Yes
417 :scope: Global
418@@ -93,25 +93,6 @@
419
420 If set to 1, ``.ibd`` file is converted (``space id``, ``index id``, etc.) with index information in ``.exp`` file during the import process (``ALTER TABLE ... IMPORT TABLESPACE`` command).
421
422- This variable was renamed to :variable:`innodb_import_table_from_xtrabackup`, beginning in release 5.5.10-20.1. It still exists as :variable:`innodb_expand_import` in versions prior to that.
423-
424-
425-.. variable:: innodb_import_table_from_xtrabackup
426-
427- :version 5.5.10-20.1: Introduced.
428- :cli: Yes
429- :conf: Yes
430- :scope: Global
431- :dyn: Yes
432- :vartype: ULONG
433- :default: 0
434- :range: 0-1
435-
436-If set to 1, ``.ibd`` file is converted (``space id``, ``index id``, etc.) with index information in .exp file during the import process (``ALTER TABLE ... IMPORT TABLESPACE`` command).
437-
438- This variable was added in release 5.5.10-20.1. Prior to that, it was named :variable:`innodb_expand_import`, which still exists in earlier versions.
439-
440-
441 .. Other Information
442
443
444
445=== modified file 'doc/source/management/innodb_extended_fast_index_creation.rst'
446--- doc/source/management/innodb_extended_fast_index_creation.rst 2012-01-30 16:43:47 +0000
447+++ doc/source/management/innodb_extended_fast_index_creation.rst 2012-12-13 13:30:28 +0000
448@@ -58,7 +58,7 @@
449 Version Specific Information
450 ============================
451
452- * 5.1.59-13.0
453+ * :rn:`5.1.59-13.0`:
454 Variable :variable:`expand_fast_index_creation` implemented.
455 This variable controls whether fast index creation optimizations made by Perocna are used.
456
457
458=== modified file 'doc/source/management/innodb_fast_index_creation.rst'
459--- doc/source/management/innodb_fast_index_creation.rst 2012-07-12 08:48:23 +0000
460+++ doc/source/management/innodb_fast_index_creation.rst 2012-12-13 13:30:28 +0000
461@@ -23,10 +23,10 @@
462 Version Specific Information
463 ============================
464
465- * 5.1.49-12.0:
466+ * :rn:`5.1.49-rel12.0`:
467 Variable :variable:`fast_index_creation` implemented.
468
469- * 5.1.56-12.7, 5.5.11-21.2:
470+ * :rn:`5.1.56-12.7`:
471 Expanded the applicability of fast index creation to :command:`mysqldump`, ``ALTER TABLE``, and ``OPTIMIZE TABLE``.
472
473
474
475=== removed file 'doc/source/management/innodb_fast_index_renaming.rst'
476--- doc/source/management/innodb_fast_index_renaming.rst 2011-10-07 00:55:06 +0000
477+++ doc/source/management/innodb_fast_index_renaming.rst 1970-01-01 00:00:00 +0000
478@@ -1,38 +0,0 @@
479-.. _innodb_fast_index_renaming:
480-
481-=====================
482- Fast Index Renaming
483-=====================
484-
485-This feature provides a way to have a fast (online) way to rename an index without rebuilding the whole table. It does this by adding a ``RENAME INDEX`` clause to the ``ALTER TABLE`` statement: ::
486-
487- ALTER TABLE ... RENAME INDEX xxx TO yyy;
488-
489-Several limitations exist:
490-
491- * The ``RENAME INDEX`` clause cannot be used with any other type of clause. If it is, an error message is displayed and an error code returned.
492-
493- * The ``RENAME INDEX`` clause can only be used when MyISAM or XtraDB is the storage engine. Otherwise, an error message will be displayed: ``wrong for the engine 'engine name'``.
494-
495- * Use of a partitioned table is not allowed. If ``ALTER TABLE`` is applied to a partitioned table, an error will occur.
496-
497- * If use of the ``RENAME INDEX`` clause results in an XtraDB error, an inconsistency between the index name in MySQL and Percona Server with XtraDB may occur.
498-
499-Errors like ``duplicate key name`` or ``key name not found`` are not caused by ``RENAME INDEX``. These errors occur before processing of the ``RENAME INDEX`` clause occurs. So they don't cause an inconsistency problem.
500-
501-An internally reserved InnoDB name (e.g., ``GEN_CLUST_INDEX``) cannot be used as an index name. If one is, an error is reported.
502-
503-If any error is returned by the ``ALTER TABLE`` command due to the ``RENAME INDEX`` clause, the best way to resolve the problem is to re-create the table.
504-
505-
506-Version Specific Information
507-============================
508-
509- * 5.1.49-12.0:
510- Not yet released externally
511-
512-Error Codes
513-===========
514-
515- * ``error_er_wrong_usage``:
516- Incorrect usage of %s and %s
517
518=== modified file 'doc/source/management/innodb_lru_dump_restore.rst'
519--- doc/source/management/innodb_lru_dump_restore.rst 2012-12-10 14:01:11 +0000
520+++ doc/source/management/innodb_lru_dump_restore.rst 2012-12-13 13:30:28 +0000
521@@ -15,7 +15,7 @@
522 Automatic Operation
523 ===================
524
525-To perform dump/restore of the buffer pool automatically, set the :variable:`innodb_lru_dump_restore` configuration variable. A non-zero value for this variable causes the server to create a new thread at startup. This thread's first task is to read and sort the saved file, and then restore the LRU accordingly.
526+To perform dump/restore of the buffer pool automatically, set the :variable:`innodb_auto_lru_dump` configuration variable. A non-zero value for this variable causes the server to create a new thread at startup. This thread's first task is to read and sort the saved file, and then restore the LRU accordingly.
527
528 After finishing the restore operation, the thread switches into dump mode, to periodically dump the LRU. The period is specified by the configuration variable's value in seconds. For example, if you set the variable to 60, then the thread saves the LRU list once per minute.
529
530
531=== modified file 'doc/source/management/sql_no_fcache.rst'
532--- doc/source/management/sql_no_fcache.rst 2011-10-07 00:55:06 +0000
533+++ doc/source/management/sql_no_fcache.rst 2012-12-13 13:30:28 +0000
534@@ -18,7 +18,7 @@
535 Version-Specific Information
536 ============================
537
538- * 5.1.49-12.0:
539+ * :rn:`5.1.49-rel12.0`:
540 Full functionality available.
541
542 Other Information
543
544=== modified file 'doc/source/management/udf_maatkit.rst'
545--- doc/source/management/udf_maatkit.rst 2011-10-07 00:55:06 +0000
546+++ doc/source/management/udf_maatkit.rst 2012-12-13 13:30:28 +0000
547@@ -15,7 +15,7 @@
548 Version Specific Information
549 ============================
550
551- * 5.1.53-12.4:
552+ * :rn:`5.1.53-12.4`:
553 Began distributing ``fnv_udf``, ``fnv1a_udf``, and ``murmur_udf``.
554
555 Other Information
556
557=== modified file 'doc/source/performance/handlersocket.rst'
558--- doc/source/performance/handlersocket.rst 2011-10-07 00:55:06 +0000
559+++ doc/source/performance/handlersocket.rst 2012-12-13 13:30:28 +0000
560@@ -19,7 +19,7 @@
561 Version Specific Information
562 ============================
563
564- * 5.1.52-12.3
565+ * :rn:`5.1.52-12.3`
566 Full functionality available.
567
568 Other Information
569
570=== modified file 'doc/source/performance/innodb_doublewrite_path.rst'
571--- doc/source/performance/innodb_doublewrite_path.rst 2011-10-07 00:55:06 +0000
572+++ doc/source/performance/innodb_doublewrite_path.rst 2012-12-13 13:30:28 +0000
573@@ -50,16 +50,16 @@
574
575 Basically if you want to improve the I/O activity, you will put the doublewrite buffer on a different disk. But is it better on an SSD or a more traditional HDD? First you should note that pages are written in a circular fashion in the doublewrite buffer and only read on recovery. So the doublewrite buffer performs mostly sequential writes and a few sequential reads. Second HDDs are very good at sequential write if a write cache is enabled, which is not the case of SSDs. Therefore you should choose a fast HDD if you want to see performance benefits from this option. For instance, you could place the redo logs (also written in a sequential way) and the doublewrite buffer on the same disk.
576
577-Prior to release 5.1.53-12.4, it was necessary to recreate your database and |InnoDB| system files when a dedicated file to contain the doublewrite buffer was specified. Beginning with release 5.1.53-12.4, you no longer need to do this.
578+Prior to release :rn:`5.1.53-12.4`, it was necessary to recreate your database and |InnoDB| system files when a dedicated file to contain the doublewrite buffer was specified. Beginning with release 5.1.53-12.4, you no longer need to do this.
579
580
581 Version Specific Information
582 ============================
583
584- * 5.1.47-11.0
585+ * :rn:`5.1.47-rel11.1`
586 Full functionality available.
587
588- * 5.1.53-12.4
589+ * :rn:`5.1.53-12.4`
590 Rebuild of database and system files no longer necessary.
591
592 System Variables
593
594=== modified file 'doc/source/performance/innodb_lazy_drop_table.rst'
595--- doc/source/performance/innodb_lazy_drop_table.rst 2012-01-27 11:37:42 +0000
596+++ doc/source/performance/innodb_lazy_drop_table.rst 2012-12-13 13:30:28 +0000
597@@ -4,14 +4,14 @@
598 Drop table performance
599 ======================
600
601-When *innodb_file_per_table* is set to 1, doing a DROP TABLE can take a long time on servers with a large buffer pool, even on an empty |InnoDB| table. This is because InnoDB has to scan through the buffer pool to purge pages that belong to the corresponding tablespace. Furthermore, no other queries can start while that scan is in progress.
602+When :variable:`innodb_file_per_table` is set to 1, doing a ``DROP TABLE`` can take a long time on servers with a large buffer pool, even on an empty |InnoDB| table. This is because InnoDB has to scan through the buffer pool to purge pages that belong to the corresponding tablespace. Furthermore, no other queries can start while that scan is in progress.
603
604 This feature allows you to do "background table drop".
605
606 Version Specific Information
607 ============================
608
609- * 5.1.56-12-7 Feature added.
610+ * :rn:`5.1.56-12.7` Feature added.
611
612 System Variables
613 ================
614@@ -26,7 +26,7 @@
615 :default: FALSE
616 :range: TRUE/FALSE
617
618-When this option is ON, XtraDB optimizes that process by only marking the pages corresponding to the tablespace being deleted. It defers the actual work of evicting those pages until it needs to find some free pages in the buffer pool.
619+When this option is ON, |XtraDB| optimizes that process by only marking the pages corresponding to the tablespace being deleted. It defers the actual work of evicting those pages until it needs to find some free pages in the buffer pool.
620
621 When this option is OFF, the usual behavior for dropping tables is in effect.
622
623
624=== modified file 'doc/source/performance/innodb_purge_thread.rst'
625--- doc/source/performance/innodb_purge_thread.rst 2011-10-07 00:55:06 +0000
626+++ doc/source/performance/innodb_purge_thread.rst 2012-12-13 13:30:28 +0000
627@@ -61,6 +61,6 @@
628
629 * `Tuning for heavy writing workloads <http://www.mysqlperformanceblog.com/2009/10/14/tuning-for-heavy-writing-workloads/>`_
630
631- * `Reasons for run-away main |InnoDB| tablespace <http://www.mysqlperformanceblog.com/2009/10/14/tuning-for-heavy-writing-workloads/>`_
632+ * `Reasons for run-away main InnoDB tablespace <http://www.mysqlperformanceblog.com/2010/06/10/reasons-for-run-away-main-innodb-tablespace/>`_
633
634- * `Purge thread spiral of death <http://www.mysqlperformanceblog.com/2009/10/14/tuning-for-heavy-writing-workloads/>`_
635+ * `Purge thread spiral of death <http://www.mysqlperformanceblog.com/2010/06/10/purge-thread-spira-of-death/>`_
636
637=== modified file 'doc/source/performance/remove_fcntl_excessive_calls.rst'
638--- doc/source/performance/remove_fcntl_excessive_calls.rst 2012-10-19 10:36:02 +0000
639+++ doc/source/performance/remove_fcntl_excessive_calls.rst 2012-12-13 13:30:28 +0000
640@@ -20,7 +20,7 @@
641 Version Specific Information
642 ============================
643
644- * :rn:`5.1.49-12.0`:
645+ * :rn:`5.1.49-rel12.0`:
646 Feature implemented
647 * :rn:`5.1.55-12.6`:
648 Feature updated
649
650=== modified file 'doc/source/release-notes/Percona-Server-5.1.50-rel12.1.rst'
651--- doc/source/release-notes/Percona-Server-5.1.50-rel12.1.rst 2012-10-13 08:58:19 +0000
652+++ doc/source/release-notes/Percona-Server-5.1.50-rel12.1.rst 2012-12-13 13:30:28 +0000
653@@ -17,7 +17,7 @@
654
655 * :ref:`innodb_buffer_pool_shm` - Implemented option :variable:`innodb_buffer_pool_shm_checksum`; when enabled, shared memory buffer pool is checksum validated. Bugs fixed: :bug:`643724`, :bug:`649408`, and :bug:`649393`. (*Yasufumi Kinoshita*)
656
657- * :ref:`innodb_expand_import_page` - Implemented more exact checking to avoid corruption of the ``.ibd`` file using :variable:`innodb_expand_export`. (*Yasufumi Kinoshita*)
658+ * :ref:`innodb_expand_import_page` - Implemented more exact checking to avoid corruption of the ``.ibd`` file using :variable:`innodb_expand_import`. (*Yasufumi Kinoshita*)
659
660 * :ref:`mysql_remove_eol_carret` - Implemented a |MySQL| client option to handle end-of-line in BLOB fields differently. Bug fixed: :bug:`625066`. (*Sasha Pachev*)
661
662
663=== renamed file 'doc/source/reliability/innodb_recovery_update_relay_log.rst' => 'doc/source/reliability/crash_resistant_replication.rst'
664--- doc/source/reliability/innodb_recovery_update_relay_log.rst 2012-06-13 10:52:23 +0000
665+++ doc/source/reliability/crash_resistant_replication.rst 2012-12-13 13:30:28 +0000
666@@ -59,7 +59,7 @@
667
668 .. variable:: innodb_overwrite_relay_log_info
669
670- :version 5.5.10-20.1: Renamed.
671+ :version 1.0.3-4: Introduced
672 :cli: Yes
673 :conf: Yes
674 :scope: Global
675
676=== modified file 'doc/source/reliability/error_pad.rst'
677--- doc/source/reliability/error_pad.rst 2011-10-07 00:55:06 +0000
678+++ doc/source/reliability/error_pad.rst 2012-12-13 13:30:28 +0000
679@@ -51,5 +51,5 @@
680 Version-Specific Information
681 ============================
682
683- * 5.1.49-12.0:
684+ * :rn:`5.1.49-rel12.0`
685 Full functionality available.
686
687=== modified file 'doc/source/reliability/log_connection_error.rst'
688--- doc/source/reliability/log_connection_error.rst 2011-10-07 00:55:06 +0000
689+++ doc/source/reliability/log_connection_error.rst 2012-12-13 13:30:28 +0000
690@@ -10,5 +10,5 @@
691 Version-Specific Information
692 ============================
693
694- * 5.1.49-12.0:
695+ * :rn:`5.1.49-rel12.0`
696 Full functionality available.
697
698=== modified file 'doc/source/reliability/show_slave_status_nolock.rst'
699--- doc/source/reliability/show_slave_status_nolock.rst 2012-09-03 09:31:43 +0000
700+++ doc/source/reliability/show_slave_status_nolock.rst 2012-12-13 13:30:28 +0000
701@@ -21,5 +21,4 @@
702 Version Specific Information
703 ============================
704
705- * 5.1.52-12.3:
706- Currently only the source code is distributed; the feature is not included in binaries.
707+ * :rn:`5.1.52-12.3` - Introduced
708
709=== modified file 'doc/source/scalability/innodb_extra_rseg.rst'
710--- doc/source/scalability/innodb_extra_rseg.rst 2012-05-29 17:18:20 +0000
711+++ doc/source/scalability/innodb_extra_rseg.rst 2012-12-13 13:30:28 +0000
712@@ -10,7 +10,9 @@
713
714 Some write-intensive workloads on boxes with many CPUs have scalability problems. The contention is caused by the rollback segment, which is single: all transactions are serialized when needing to access the segment. With this feature you can now create and use multiple segments (up to 256).
715
716-**NOTE**: This feature is incompatible with |InnoDB|. As long as a single rollback segment is used, there is no problem; the database can still be used by both |XtraDB| and |InnoDB|. However, creating multiple rollback segments will cause an internal format change to the system tablespace. Once multiple segments have been created, the database will no longer be compatible with |InnoDB|.
717+.. note::
718+
719+ This feature is incompatible with |InnoDB|. As long as a single rollback segment is used, there is no problem; the database can still be used by both |XtraDB| and |InnoDB|. However, creating multiple rollback segments will cause an internal format change to the system tablespace. Once multiple segments have been created, the database will no longer be compatible with |InnoDB|.
720
721
722 System Variables
723@@ -40,8 +42,6 @@
724
725 The result should be the number of extra segments + 1 (as a default single segment always exists).
726
727- This variable has been removed from |Percona Server| 5.5.11-20.2 because an equivalent variable, ``innodb_rollback_segment``, has been implemented in |MySQL| 5.5.
728-
729
730 ``INFORMATION_SCHEMA`` Tables
731 =============================
732
733=== modified file 'doc/source/scalability/innodb_io.rst'
734--- doc/source/scalability/innodb_io.rst 2012-10-05 10:57:57 +0000
735+++ doc/source/scalability/innodb_io.rst 2012-12-13 13:30:28 +0000
736@@ -36,7 +36,7 @@
737
738 .. variable:: innodb_adaptive_checkpoint
739
740- :version: 5.1.54-12.5 Added
741+ :version 5.1.54-12.5: Added
742 :cli: Yes
743 :conf: Yes
744 :scope: Global
745@@ -109,7 +109,7 @@
746
747 .. variable:: innodb_flush_log_at_trx_commit_session
748
749- :version: 5.1.49-13 Added
750+ :version 5.1.49-rel11.3: Added
751 :cli: Yes
752 :conf: Yes
753 :scope: Global

Subscribers

People subscribed via source and target branches