Percona Server moved to https://jira.percona.com/projects/PS

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

  1. docversionsplit-5.5
  2. Merge into 5.5
Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Stewart Smith
Approved revision: no longer in the source branch.
Merged at revision: 218
Proposed branch: lp:~hrvojem/percona-server/docversionsplit-5.5
Merge into: lp:percona-server/5.5
Diff against target: 749 lines (+155/-335)
21 files modified
doc/source/conf.py (+2/-2)
doc/source/diagnostics/innodb_deadlock_count.rst (+4/-4)
doc/source/diagnostics/mysql_syslog.rst (+1/-0)
doc/source/diagnostics/response_time_distribution.rst (+6/-9)
doc/source/diagnostics/show_engines.rst (+1/-1)
doc/source/feature_comparison.rst (+128/-61)
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 (+1/-33)
doc/source/flexibility/mysql_remove_eol_carret.rst (+1/-1)
doc/source/flexibility/replication_skip_single_statement.rst (+0/-167)
doc/source/index.rst (+0/-2)
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/performance/handlersocket.rst (+1/-1)
doc/source/performance/innodb_doublewrite_path.rst (+1/-6)
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)
To merge this branch: bzr merge lp:~hrvojem/percona-server/docversionsplit-5.5
Reviewer Review Type Date Requested Status
Stewart Smith (community) Approve
Review via email: mp+92722@code.launchpad.net
To post a comment you must log in.
Revision history for this message
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/conf.py'
2--- doc/source/conf.py 2012-02-03 10:23:20 +0000
3+++ doc/source/conf.py 2012-02-13 08:57:19 +0000
4@@ -45,7 +45,7 @@
5
6 # General information about the project.
7 project = u'Percona Server'
8-copyright = u'2012, Percona Inc'
9+copyright = u'2011-2012, Percona Inc'
10
11 # The version info for the project you're documenting, acts as replacement for
12 # |version| and |release|, also used in various other places throughout the
13@@ -54,7 +54,7 @@
14 # The short X.Y version.
15 version = '5.5'
16 # The full version, including alpha/beta/rc tags.
17-release = '15'
18+release = '20'
19
20 # The language for content autogenerated by Sphinx. Refer to documentation
21 # for a list of supported languages.
22
23=== modified file 'doc/source/diagnostics/innodb_deadlock_count.rst'
24--- doc/source/diagnostics/innodb_deadlock_count.rst 2011-10-07 23:38:41 +0000
25+++ doc/source/diagnostics/innodb_deadlock_count.rst 2012-02-13 08:57:19 +0000
26@@ -1,4 +1,4 @@
27-.. _innodb_deadlock_count:
28+.. _innodb_deadlocks_page:
29
30 ==========================
31 Count |InnoDB| Deadlocks
32@@ -14,7 +14,7 @@
33
34 You can use it with ``SHOW GLOBAL STATUS``, e.g.: ::
35
36- mysql> SHOW GLOBAL_STATUS LIKE ``innodb_deadlocks``;
37+ mysql> SHOW GLOBAL STATUS LIKE 'innodb_deadlocks';
38 +------------------+-------+
39 | Variable_name | Value |
40 +------------------+-------+
41@@ -23,7 +23,7 @@
42
43 or with ``INFORMATION_SCHEMA``, e.g.: ::
44
45- mysql> SELECT VARIABLE_VALUE FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = ``innodb_deadlocks``;
46+ mysql> SELECT VARIABLE_VALUE FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'innodb_deadlocks';
47 +----------------+
48 | VARIABLE_VALUE |
49 +----------------+
50@@ -36,7 +36,7 @@
51 Version Specific Information
52 ============================
53
54- * 5.1.47-11.0:
55+ * 5.5.8-20.0:
56 Full functionality available.
57
58 Status Variables
59
60=== modified file 'doc/source/diagnostics/mysql_syslog.rst'
61--- doc/source/diagnostics/mysql_syslog.rst 2011-10-07 23:38:41 +0000
62+++ doc/source/diagnostics/mysql_syslog.rst 2012-02-13 08:57:19 +0000
63@@ -26,6 +26,7 @@
64
65 :cli: Yes
66 :conf: Yes
67+ :server: No
68 :scope: Global
69 :dyn: Yes
70 :vartype: Boolean
71
72=== modified file 'doc/source/diagnostics/response_time_distribution.rst'
73--- doc/source/diagnostics/response_time_distribution.rst 2011-10-07 23:38:41 +0000
74+++ doc/source/diagnostics/response_time_distribution.rst 2012-02-13 08:57:19 +0000
75@@ -193,21 +193,18 @@
76 Version Specific Information
77 ============================
78
79- * 5.1.49-12.0:
80- Full functionality available.
81-
82- * 5.1.53-12.4:
83- Introduced have_response_time_distribution.
84-
85- * 5.5.8-20.0:
86- Renamed variable :variable:`enable_query_response_time_stats` to :variable:`query_response_time_stats`.
87+ * 5.5.8-20.0:
88+ Introduced variable variable:`have_response_time_distribution`.
89+
90+ * 5.5.8-20.0:
91+ Introduced variable variable:`query_response_time_stats`.
92
93 System Variables
94 ================
95
96 .. variable:: have_response_time_distribution
97
98- :version 5.1.53-12.4: Introduced.
99+ :version 5.5.8-20.0: Introduced.
100 :scope: Global
101 :dyn: No
102 :vartype: Boolean
103
104=== modified file 'doc/source/diagnostics/show_engines.rst'
105--- doc/source/diagnostics/show_engines.rst 2011-10-07 23:38:41 +0000
106+++ doc/source/diagnostics/show_engines.rst 2012-02-13 08:57:19 +0000
107@@ -29,7 +29,7 @@
108 Version-Specific Information
109 ============================
110
111- * 5.1.49-12.0:
112+ * 5.5.8-20.0:
113 Full functionality available.
114
115 Other Information
116
117=== modified file 'doc/source/feature_comparison.rst'
118--- doc/source/feature_comparison.rst 2011-09-20 07:03:00 +0000
119+++ doc/source/feature_comparison.rst 2012-02-13 08:57:19 +0000
120@@ -20,65 +20,132 @@
121
122 We provide these benefits by significantly enhancing |Percona Server| as compared to the standard |MySQL| database server:
123
124-.. raw:: html
125-
126- <table class="datatable">
127- <tr><th class="label">Feature</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr>
128- <tr><td class="label">Open source</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
129- <tr><td class="label">ACID Compliance</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
130- <tr><td class="label">Multi-Version Concurrency Control</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
131- <tr><td class="label">Row-Level Locking</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
132- <tr><td class="label">Automatic Crash Recovery</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
133- <tr><td class="label">Table Partitioning</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
134- <tr><td class="label">Views</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
135- <tr><td class="label">Subqueries</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
136- <tr><td class="label">Triggers</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
137- <tr><td class="label">Stored Procedures</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
138- <tr><td class="label">Foreign Keys</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
139- <tr><th class="label">Extra Features for Developers</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr>
140- <tr><td class="label">NoSQL Socket-Level Interface</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
141- <tr><td class="label">Extra Hash/Digest Functions</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
142- <tr><th class="label">Extra Diagnostic Features</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr>
143- <tr><td class="label">PERFORMANCE_SCHEMA Diagnostics Tables</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
144- <tr><td class="label">INFORMATION_SCHEMA Tables</td><td>60</td><td>37</td></tr>
145- <tr><td class="label">Global Performance and Status Counters</td><td>366</td><td>308</td></tr>
146- <tr><td class="label">Per-Table Performance Counters</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
147- <tr><td class="label">Per-Index Performance Counters</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
148- <tr><td class="label">Per-User Performance Counters</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
149- <tr><td class="label">Per-Client Performance Counters</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
150- <tr><td class="label">High-Resolution Process List Timing</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
151- <tr><td class="label">Detailed Query Execution and Plan Log</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
152- <tr><td class="label">Global Query Response Time Statistics</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
153- <tr><td class="label">InnoDB Data Dictionary as I_S Tables</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
154- <tr><td class="label">Access to InnoDB Data Statistics</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
155- <tr><td class="label">Enhanced SHOW INNODB STATUS</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
156- <tr><td class="label">Enhanced Mutex Diagnostics</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
157- <tr><th class="label">Durability and Reliability Enhancements</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr>
158- <tr><td class="label">Transactional Replication State</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
159- <tr><td class="label">Handles Corrupted Tables Gracefully</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
160- <tr><th class="label">Performance &amp; Scalability Enhancements</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr>
161- <tr><td class="label">Support for &gt; 1024 Concurrent Transactions</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
162- <tr><td class="label">Support for Multiple I/O Threads</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
163- <tr><td class="label">Dedicated Purge Threads</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td></tr>
164- <tr><td class="label">Self-Tuning Checkpoint Algorithm</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
165- <tr><td class="label">Fine-Grained Mutex Locking</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
166- <tr><td class="label">Lock-Free Algorithms</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
167- <tr><td class="label">Partitioned Adaptive Hash Search</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
168- <tr><td class="label">Separate Doublewrite File</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
169- <tr><td class="label">Fast Checksum Algorithm</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
170- <tr><td class="label">Buffer Pool Pre-Load</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
171- <tr><td class="label">Fast Shut-Down</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
172- <tr><td class="label">Support for FlashCache</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
173- <tr><td class="label">Read-Ahead Improvements</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
174- <tr><th class="label">Extra Features for DBA/Operations Staff</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr>
175- <tr><td class="label">Configurable Page Sizes</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
176- <tr><td class="label">Shared-Memory Buffer Pool</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
177- <tr><td class="label">Import Tables From Different Servers</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
178- <tr><td class="label">Configurable Data Dictionary Size</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
179- <tr><td class="label">Configurable Insert Buffer Size</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
180- <tr><td class="label">Active Change Buffer Purging</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
181- <tr><td class="label">Error/Warning Logging Enhancements</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
182- <tr><td class="label">Configurable Fast Index Creation</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
183- <tr><td class="label">Fast Index Renaming</td><td><img src="http://s0.percona.com/check-yes.png" alt="Yes" width="24" height="24" /></td><td></td></tr>
184- </table>
185++---------------------------------------+----------------------+--------------+
186+|Features |Percona Server 5.5.20 |MySQL 5.5.20 |
187++=======================================+======================+==============+
188+|Open source | Yes | Yes |
189++---------------------------------------+----------------------+--------------+
190+|ACID Compliance | Yes | Yes |
191++---------------------------------------+----------------------+--------------+
192+|Multi-Version Concurrency Control | Yes | Yes |
193++---------------------------------------+----------------------+--------------+
194+|Row-Level Locking | Yes | Yes |
195++---------------------------------------+----------------------+--------------+
196+|Automatic Crash Recovery | Yes | Yes |
197++---------------------------------------+----------------------+--------------+
198+|Table Partitioning | Yes | Yes |
199++---------------------------------------+----------------------+--------------+
200+|Views | Yes | Yes |
201++---------------------------------------+----------------------+--------------+
202+|Subqueries | Yes | Yes |
203++---------------------------------------+----------------------+--------------+
204+|Triggers | Yes | Yes |
205++---------------------------------------+----------------------+--------------+
206+|Stored Procedures | Yes | Yes |
207++---------------------------------------+----------------------+--------------+
208+|Foreign Keys | Yes | Yes |
209++---------------------------------------+----------------------+--------------+
210+
211++---------------------------------------+----------------------+--------------+
212+|Extra Features for Developers |Percona Server 5.5.20 |MySQL 5.5.20 |
213++=======================================+======================+==============+
214+|NoSQL Socket-Level Interface | Yes | |
215++---------------------------------------+----------------------+--------------+
216+|Extra Hash/Digest Functions | Yes | |
217++---------------------------------------+----------------------+--------------+
218+
219++---------------------------------------+----------------------+--------------+
220+|Extra Diagnostic Features |Percona Server 5.5.20 |MySQL 5.5.20 |
221++=======================================+======================+==============+
222+|INFORMATION_SCHEMA Tables | 60 | 37 |
223++---------------------------------------+----------------------+--------------+
224+|Global Performance and Status Counters | 370 | 310 |
225++---------------------------------------+----------------------+--------------+
226+|Per-Table Performance Counters | Yes | |
227++---------------------------------------+----------------------+--------------+
228+|Per-Index Performance Counters | Yes | |
229++---------------------------------------+----------------------+--------------+
230+|Per-User Performance Counters | Yes | |
231++---------------------------------------+----------------------+--------------+
232+|Per-Client Performance Counters | Yes | |
233++---------------------------------------+----------------------+--------------+
234+|Per-Thread Performance Counters | Yes | |
235++---------------------------------------+----------------------+--------------+
236+|High-Resolution Process List Timing | Yes | |
237++---------------------------------------+----------------------+--------------+
238+|Detailed Query Execution and Plan Log | Yes | |
239++---------------------------------------+----------------------+--------------+
240+|Global Query Response Time Statistics | Yes | |
241++---------------------------------------+----------------------+--------------+
242+|InnoDB Data Dictionary as I_S Tables | Yes | |
243++---------------------------------------+----------------------+--------------+
244+|Access to InnoDB Data Statistics | Yes | |
245++---------------------------------------+----------------------+--------------+
246+|Enhanced SHOW INNODB STATUS | Yes | |
247++---------------------------------------+----------------------+--------------+
248+|Enhanced Mutex Diagnostics | Yes | |
249++---------------------------------------+----------------------+--------------+
250+
251++---------------------------------------+----------------------+--------------+
252+|Durability and Reliability Enhancements|Percona Server 5.5.20 |MySQL 5.5.20 |
253++=======================================+======================+==============+
254+|Transactional Replication State | Yes | |
255++---------------------------------------+----------------------+--------------+
256+|Handles Corrupted Tables Gracefully | Yes | |
257++---------------------------------------+----------------------+--------------+
258+
259++---------------------------------------+----------------------+--------------+
260+|Performance & Scalability Enhancements |Percona Server 5.5.20 |MySQL 5.5.20 |
261++=======================================+======================+==============+
262+|Support for Multiple I/O Threads | Yes | Yes |
263++---------------------------------------+----------------------+--------------+
264+|Dedicated Purge Threads | Yes | Yes |
265++---------------------------------------+----------------------+--------------+
266+|Self-Tuning Checkpoint Algorithm | Yes | |
267++---------------------------------------+----------------------+--------------+
268+|Fine-Grained Mutex Locking | Yes | |
269++---------------------------------------+----------------------+--------------+
270+|Lock-Free Algorithms | Yes | |
271++---------------------------------------+----------------------+--------------+
272+|Improved MEMORY Storage Engine | Yes | |
273++---------------------------------------+----------------------+--------------+
274+|Partitioned Adaptive Hash Search | Yes | |
275++---------------------------------------+----------------------+--------------+
276+|Separate Doublewrite File | Yes | |
277++---------------------------------------+----------------------+--------------+
278+|Fast Checksum Algorithm | Yes | |
279++---------------------------------------+----------------------+--------------+
280+|Buffer Pool Pre-Load | Yes | |
281++---------------------------------------+----------------------+--------------+
282+|Fast Shut-Down | Yes | |
283++---------------------------------------+----------------------+--------------+
284+|Background Table Drop | Yes | |
285++---------------------------------------+----------------------+--------------+
286+|Support for FlashCache | Yes | |
287++---------------------------------------+----------------------+--------------+
288+|Read-Ahead Improvements | Yes | |
289++---------------------------------------+----------------------+--------------+
290+
291++---------------------------------------+----------------------+--------------+
292+|Extra Features for DBA/Operations Staff|Percona Server 5.5.20 |MySQL 5.5.20 |
293++=======================================+======================+==============+
294+|Configurable Page Sizes | Yes | |
295++---------------------------------------+----------------------+--------------+
296+|Import Tables From Different Servers | Yes | |
297++---------------------------------------+----------------------+--------------+
298+|Configurable Data Dictionary Size | Yes | |
299++---------------------------------------+----------------------+--------------+
300+|Configurable Insert Buffer Size | Yes | |
301++---------------------------------------+----------------------+--------------+
302+|Active Change Buffer Purging | Yes | |
303++---------------------------------------+----------------------+--------------+
304+|Error/Warning Logging Enhancements | Yes | |
305++---------------------------------------+----------------------+--------------+
306+|Configurable Fast Index Creation | Yes | |
307++---------------------------------------+----------------------+--------------+
308+|Fast Index Renaming | Yes | |
309++---------------------------------------+----------------------+--------------+
310+|Support for Fake Changes | Yes | |
311++---------------------------------------+----------------------+--------------+
312+
313
314
315=== modified file 'doc/source/flexibility/buff_read_ahead_area.rst'
316--- doc/source/flexibility/buff_read_ahead_area.rst 2011-10-07 23:38:41 +0000
317+++ doc/source/flexibility/buff_read_ahead_area.rst 2012-02-13 08:57:19 +0000
318@@ -18,7 +18,7 @@
319 Version Specific Information
320 ============================
321
322- * :rn:`5.1.47-12.0` :
323+ * :rn:`5.5.8-20.0` :
324 Full functionality available.
325
326 Other Information
327
328=== modified file 'doc/source/flexibility/innodb_fast_shutdown.rst'
329--- doc/source/flexibility/innodb_fast_shutdown.rst 2011-10-07 23:38:41 +0000
330+++ doc/source/flexibility/innodb_fast_shutdown.rst 2012-02-13 08:57:19 +0000
331@@ -15,7 +15,7 @@
332 Version Specific Information
333 ============================
334
335- * 5.1.52-12.3:
336+ * 5.5.8-20
337 Full functionality available.
338
339 Other Information
340
341=== modified file 'doc/source/flexibility/log_warnings_suppress.rst'
342--- doc/source/flexibility/log_warnings_suppress.rst 2011-10-07 23:38:41 +0000
343+++ doc/source/flexibility/log_warnings_suppress.rst 2012-02-13 08:57:19 +0000
344@@ -10,44 +10,12 @@
345 Version Specific Information
346 ============================
347
348- * 5.1.47-11.0:
349- System variable :variable:`suppress_log_warning_1592` introduced.
350-
351 * 5.5.8-20.0:
352- System variable :variable:`suppress_log_warning_1592` replaced by :variable:`log_warnings_silence`.
353+ System variable :variable:`log_warnings_silence` introduced.
354
355 * 5.5.10-20.1:
356 Renamed variable :variable:`log_warnings_silence` to :variable:`log_warnings_suppress`.
357
358-System Variables
359-================
360-
361-.. variable:: suppress_log_warning_1592
362-
363- :version 5.1.47-11.0: Introduced.
364- :version 5.5.8-20.0: Deleted.
365- :cli: Yes
366- :conf: Yes
367- :scope: Global
368- :dyn: Yes
369- :vartype: Boolean
370- :default: OFF
371- :range: ON(='1592') / OFF
372-
373-This has no effect on replication, but it can fill up your error log with unnecessary messages. This variable allows you to completely disable logging of this warning.
374-
375-**NOTE:** Only |MySQL| 5.1 is subject to this bug. A partial solution has been published beginning with |MySQL| 5.1.37, but this bug still appears in some situations.
376-
377-When ``ON``, disables reporting of warning #1592 (unsafe statement for binary logging).
378-
379-All warnings #1592 will be disabled, so you will not be able to know if your statements are really safe to replicate anymore. Use it at your own risk and only if you understand what you are doing.
380-
381-In some circumstances, |MySQL| will warn you that a statement is unsafe to replicate even though it is perfectly safe. For example: ::
382-
383- 090213 16:58:54 [Warning] Statement is not safe to log in statement format.
384-
385-This variable was obsoleted, beginning in release 5.5.8-20.0. It still exists in versions 5.1.47-11.0 to 5.1.54-12.5.
386-
387 .. variable:: log_warnings_suppress
388
389 :version 5.5.8-20.0: Introduced.
390
391=== modified file 'doc/source/flexibility/mysql_remove_eol_carret.rst'
392--- doc/source/flexibility/mysql_remove_eol_carret.rst 2011-10-07 23:38:41 +0000
393+++ doc/source/flexibility/mysql_remove_eol_carret.rst 2012-02-13 08:57:19 +0000
394@@ -14,7 +14,7 @@
395 Version Specific Information
396 ============================
397
398- * 5.1.50-12.1:
399+ * 5.5.8-20.0:
400 Full functionality.
401
402 Client Command Line Parameter
403
404=== removed file 'doc/source/flexibility/replication_skip_single_statement.rst'
405--- doc/source/flexibility/replication_skip_single_statement.rst 2011-10-07 23:38:41 +0000
406+++ doc/source/flexibility/replication_skip_single_statement.rst 1970-01-01 00:00:00 +0000
407@@ -1,167 +0,0 @@
408-.. _replication_skip_single_statement:
409-
410-===========================
411- Replication Stop Recovery
412-===========================
413-
414-After a replication stop, this feature allows skipping a user-specified number of events from the binary log, rather than all events remaining in the current event group.
415-
416-The discussion of the system variable ``sql_slave_skip_counter`` in the `MySQL 5.1 Reference Manual notes <http://dev.mysql.com/doc/refman/5.1/en/set-global-sql-slave-skip-counter.html>`_:
417-
418-When using this statement, it is important to understand that the binary log is actually organized
419-as a sequence of groups known as event groups. Each event group consists of a sequence of events.
420-
421- * For transactional tables, an event group corresponds to a transaction.
422-
423- * For nontransactional tables, an event group corresponds to a single SQL statement.
424-
425-A single transaction can contain changes to both transactional and nontransactional tables.
426-
427-When you use SET GLOBAL sql_slave_skip_counter to skip events and the result is in the middle of a group, the slave continues to skip events until it reaches the end of the group. Execution then starts with the next event group.
428-
429-When used, this feature modifies the standard |MySQL| behavior described above. It provides the user additional flexibility in recovering from a replication stop, but it should be used with caution. In particular, :variable:`sql_slave_statement_skip_counter` and ``sql_slave_skip_counter`` should not be used at the same time (i.e., they should not both be non-zero), as this may cause unintended behavior.
430-
431-
432-Version Specific Information
433-============================
434-
435- * 5.1.49-12.0:
436- Full functionality released.
437-
438-System Variables
439-================
440-
441-The following status variable was introduced by this feature.
442-
443-.. variable:: sql_slave_statement_skip_counter
444-
445- :cli: Yes
446- :conf: Yes
447- :scope: Global
448- :dyn: Yes
449- :vartype: Numeric
450- :default: 0
451- :range: 1-MAXLONGINT
452-
453-This variable specifies the number of events in the current event group to skip.
454-
455-**IMPORTANT:** As mentioned above, never set both this variable and sql_slave_skip_counter to non-zero values at the same time. The behavior that will result from this is unknown.
456-
457-Consider this case: ::
458-
459- SET GLOBAL sql_slave_statement_skip_counter=n;
460- SET GLOBAL sql_slave__skip_counter=m;
461-
462-The first statement will skip the next ``n`` events in the current event group. At that point, one would expect the second statement to operate as described in the |MySQL| documentation for ``sql_slave_skip_counter``. However, depending on the values of ``n`` and ``m`` and the contents of the binary log, the effects of the interactions of the two statements can involve very complicated scenarios. **THESE SCENARIOS HAVE NOT BEEN TESTED**.
463-
464-Example
465-=======
466-
467-In the example here, a master server with two slaves is assumed. A table is created on the master and then a replication error occurs.
468-
469-Then the difference between using the new system variable :variable:`sql_slave_statement_skip_counter` and the |MySQL| system variable ``sql_slave_skip_counter`` to repair the replication stop is shown.
470-
471-Setup
472------
473-
474- - Prepare the master server: ::
475-
476- DROP TABLE IF EXISTS t;
477- CREATE TABLE t(id INT UNIQUE PRIMARY KEY) ENGINE=|InnoDB|;
478- INSERT INTO t VALUES (1),(2);
479-
480- - Prepare Slave #1 and Slave #2: ::
481-
482- DROP TABLE IF EXISTS t;
483- CREATE TABLE t(id INT UNIQUE PRIMARY KEY) ENGINE=|InnoDB|;
484- INSERT INTO t VALUES (1),(2),(3),(5);
485-
486- - Start replication of the master to the two slaves.
487-
488-Create the Replication Error
489-----------------------------
490-
491-Run the following on the master: ::
492-
493- START TRANSACTION;
494- INSERT INTO t VALUES (3);
495- INSERT INTO t VALUES (4);
496- COMMIT;
497-
498-Both slaves will fail with the following error: ::
499-
500- Error ``Duplicate entry ``3`` for key ``PRIMARY```` on query. Default database: ``test``. Query: ``INSERT INTO t VALUES (3)``
501-
502-Repair the Replication Error
503-----------------------------
504-
505-Now, let's compare the effects of using ``sql_slave_skip_counter`` to do the repair versus using :variable:`sql_slave_statement_skip_counter` to do it.
506-
507-Slave Repair Using sql_slave_skip_counter
508-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
509-
510-To repair either slave, do the following: ::
511-
512- SET GLOBAL sql_slave_skip_counter=1;
513- START SLAVE;
514-
515-This will cause the slave to skip the following statement: ::
516-
517- INSERT INTO t VALUES (3);
518-
519-In addition, since we are in the middle of an event group in the binary log, all other events in the event group will also be skipped, since that is the standard behavior of ``sql_slave_skip_counter``. In this case, the following statements will also be skipped: ::
520-
521- INSERT INTO t VALUES (4);
522- COMMIT;
523-
524-Now run the following on the slave: ::
525-
526- SELECT * FROM t;
527-
528-This will give the result: ::
529-
530- id
531- 1
532- 2
533- 3
534- 5
535-
536-Since the table's original contents are unchanged, this shows that ``sql_slave_skip_counter`` caused the entire event group to be skipped.
537-
538-Slave Repair Using sql_slave_statement_skip_counter
539-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
540-
541-To repair either slave, do the following: ::
542-
543- SET GLOBAL sql_slave_statement_skip_counter=1;
544- START SLAVE;
545-
546-This will cause the slave to skip the following statement: ::
547-
548- INSERT INTO t VALUES (3);
549-
550-However, unlike with ``sql_slave_skip_counter``, this is the only event that will be skipped. Every other event in the current event group in the binary log will be executed. In this case, that means these statements will not be skipped; they will also be executed: ::
551-
552- INSERT INTO t VALUES (4);
553- COMMIT;
554-
555-Now, we can see the difference in results when we run: ::
556-
557- SELECT * FROM t;
558-
559-Now, our results are: ::
560-
561- id
562- 1
563- 2
564- 3
565- 4
566- 5
567-
568-In this case, ``sql_slave_statement_skip_counter`` caused the server to skip only single statement, not the entire remainder of the event group. The result is that the original table has been updated.
569-
570-
571-Other Reading
572--------------
573-
574- * `MySQL 5.1 Reference Manual - "SET GLOBAL sql_slave_skip_counter Syntax" <http://dev.mysql.com/doc/refman/5.1/en/set-global-sql-slave-skip-counter.html>`_
575
576=== modified file 'doc/source/index.rst'
577--- doc/source/index.rst 2012-02-03 10:23:20 +0000
578+++ doc/source/index.rst 2012-02-13 08:57:19 +0000
579@@ -88,7 +88,6 @@
580 flexibility/innodb_files_extend
581 flexibility/log_warnings_suppress
582 flexibility/mysql_remove_eol_carret
583- flexibility/replication_skip_single_statement
584 flexibility/buff_read_ahead_area
585 flexibility/innodb_fast_shutdown
586 flexibility/improved_memory_engine
587@@ -119,7 +118,6 @@
588 management/innodb_lru_dump_restore
589 management/innodb_fast_index_creation
590 management/innodb_extended_fast_index_creation
591- management/innodb_fast_index_renaming
592 management/sql_no_fcache
593 management/udf_maatkit
594 management/innodb_fake_changes
595
596=== modified file 'doc/source/management/innodb_fast_index_creation.rst'
597--- doc/source/management/innodb_fast_index_creation.rst 2011-10-07 23:38:41 +0000
598+++ doc/source/management/innodb_fast_index_creation.rst 2012-02-13 08:57:19 +0000
599@@ -44,10 +44,10 @@
600 Version Specific Information
601 ============================
602
603- * 5.1.49-12.0:
604+ * 5.5.8-20.0:
605 Variable :variable:`fast_index_creation` implemented.
606
607- * 5.1.56-12.7, 5.5.11-21.2:
608+ * 5.5.11-21.2:
609 Expanded the applicability of fast index creation to :command:`mysqldump`, ``ALTER TABLE``, and ``OPTIMIZE TABLE``.
610
611
612
613=== removed file 'doc/source/management/innodb_fast_index_renaming.rst'
614--- doc/source/management/innodb_fast_index_renaming.rst 2011-10-07 23:38:41 +0000
615+++ doc/source/management/innodb_fast_index_renaming.rst 1970-01-01 00:00:00 +0000
616@@ -1,38 +0,0 @@
617-.. _innodb_fast_index_renaming:
618-
619-=====================
620- Fast Index Renaming
621-=====================
622-
623-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: ::
624-
625- ALTER TABLE ... RENAME INDEX xxx TO yyy;
626-
627-Several limitations exist:
628-
629- * 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.
630-
631- * 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'``.
632-
633- * Use of a partitioned table is not allowed. If ``ALTER TABLE`` is applied to a partitioned table, an error will occur.
634-
635- * 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.
636-
637-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.
638-
639-An internally reserved InnoDB name (e.g., ``GEN_CLUST_INDEX``) cannot be used as an index name. If one is, an error is reported.
640-
641-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.
642-
643-
644-Version Specific Information
645-============================
646-
647- * 5.1.49-12.0:
648- Not yet released externally
649-
650-Error Codes
651-===========
652-
653- * ``error_er_wrong_usage``:
654- Incorrect usage of %s and %s
655
656=== modified file 'doc/source/management/innodb_lru_dump_restore.rst'
657--- doc/source/management/innodb_lru_dump_restore.rst 2011-10-07 23:38:41 +0000
658+++ doc/source/management/innodb_lru_dump_restore.rst 2012-02-13 08:57:19 +0000
659@@ -105,7 +105,7 @@
660 Version Specific Information
661 ============================
662
663- * 5.1.50-12.1:
664+ * 5.5.8-20.0:
665 Automatic dump/restore implemented.
666 * 5.5.10-20.1:
667 Renamed variable :variable:`innodb_auto_lru_dump` to :variable:`innodb_buffer_pool_restore_at_startup`.
668
669=== modified file 'doc/source/management/sql_no_fcache.rst'
670--- doc/source/management/sql_no_fcache.rst 2011-10-07 23:38:41 +0000
671+++ doc/source/management/sql_no_fcache.rst 2012-02-13 08:57:19 +0000
672@@ -18,7 +18,7 @@
673 Version-Specific Information
674 ============================
675
676- * 5.1.49-12.0:
677+ * 5.5.8-20.0:
678 Full functionality available.
679
680 Other Information
681
682=== modified file 'doc/source/performance/handlersocket.rst'
683--- doc/source/performance/handlersocket.rst 2011-10-07 23:38:41 +0000
684+++ doc/source/performance/handlersocket.rst 2012-02-13 08:57:19 +0000
685@@ -19,7 +19,7 @@
686 Version Specific Information
687 ============================
688
689- * 5.1.52-12.3
690+ * 5.5.11-20.2
691 Full functionality available.
692
693 Other Information
694
695=== modified file 'doc/source/performance/innodb_doublewrite_path.rst'
696--- doc/source/performance/innodb_doublewrite_path.rst 2011-10-07 23:38:41 +0000
697+++ doc/source/performance/innodb_doublewrite_path.rst 2012-02-13 08:57:19 +0000
698@@ -50,17 +50,12 @@
699
700 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.
701
702-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.
703-
704-
705 Version Specific Information
706 ============================
707
708- * 5.1.47-11.0
709+ * 5.5.8-20.0
710 Full functionality available.
711
712- * 5.1.53-12.4
713- Rebuild of database and system files no longer necessary.
714
715 System Variables
716 ================
717
718=== modified file 'doc/source/reliability/error_pad.rst'
719--- doc/source/reliability/error_pad.rst 2011-10-07 23:38:41 +0000
720+++ doc/source/reliability/error_pad.rst 2012-02-13 08:57:19 +0000
721@@ -51,5 +51,5 @@
722 Version-Specific Information
723 ============================
724
725- * 5.1.49-12.0:
726+ * 5.5.8-20.0
727 Full functionality available.
728
729=== modified file 'doc/source/reliability/log_connection_error.rst'
730--- doc/source/reliability/log_connection_error.rst 2011-10-07 23:38:41 +0000
731+++ doc/source/reliability/log_connection_error.rst 2012-02-13 08:57:19 +0000
732@@ -10,5 +10,5 @@
733 Version-Specific Information
734 ============================
735
736- * 5.1.49-12.0:
737+ * 5.5.8-20.0:
738 Full functionality available.
739
740=== modified file 'doc/source/reliability/show_slave_status_nolock.rst'
741--- doc/source/reliability/show_slave_status_nolock.rst 2011-10-07 23:38:41 +0000
742+++ doc/source/reliability/show_slave_status_nolock.rst 2012-02-13 08:57:19 +0000
743@@ -20,5 +20,4 @@
744 Version Specific Information
745 ============================
746
747- * 5.1.52-12.3:
748- Currently only the source code is distributed; the feature is not included in binaries.
749+ * 5.5.8-20.0:

Subscribers

People subscribed via source and target branches