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
=== modified file 'doc/source/conf.py'
--- doc/source/conf.py 2012-02-03 10:23:20 +0000
+++ doc/source/conf.py 2012-02-13 08:57:19 +0000
@@ -45,7 +45,7 @@
4545
46# General information about the project.46# General information about the project.
47project = u'Percona Server'47project = u'Percona Server'
48copyright = u'2012, Percona Inc'48copyright = u'2011-2012, Percona Inc'
4949
50# The version info for the project you're documenting, acts as replacement for50# The version info for the project you're documenting, acts as replacement for
51# |version| and |release|, also used in various other places throughout the51# |version| and |release|, also used in various other places throughout the
@@ -54,7 +54,7 @@
54# The short X.Y version.54# The short X.Y version.
55version = '5.5'55version = '5.5'
56# The full version, including alpha/beta/rc tags.56# The full version, including alpha/beta/rc tags.
57release = '15'57release = '20'
5858
59# The language for content autogenerated by Sphinx. Refer to documentation59# The language for content autogenerated by Sphinx. Refer to documentation
60# for a list of supported languages.60# for a list of supported languages.
6161
=== modified file 'doc/source/diagnostics/innodb_deadlock_count.rst'
--- doc/source/diagnostics/innodb_deadlock_count.rst 2011-10-07 23:38:41 +0000
+++ doc/source/diagnostics/innodb_deadlock_count.rst 2012-02-13 08:57:19 +0000
@@ -1,4 +1,4 @@
1.. _innodb_deadlock_count:1.. _innodb_deadlocks_page:
22
3==========================3==========================
4 Count |InnoDB| Deadlocks4 Count |InnoDB| Deadlocks
@@ -14,7 +14,7 @@
1414
15You can use it with ``SHOW GLOBAL STATUS``, e.g.: ::15You can use it with ``SHOW GLOBAL STATUS``, e.g.: ::
1616
17 mysql> SHOW GLOBAL_STATUS LIKE ``innodb_deadlocks``;17 mysql> SHOW GLOBAL STATUS LIKE 'innodb_deadlocks';
18 +------------------+-------+18 +------------------+-------+
19 | Variable_name | Value |19 | Variable_name | Value |
20 +------------------+-------+20 +------------------+-------+
@@ -23,7 +23,7 @@
2323
24or with ``INFORMATION_SCHEMA``, e.g.: ::24or with ``INFORMATION_SCHEMA``, e.g.: ::
2525
26 mysql> SELECT VARIABLE_VALUE FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = ``innodb_deadlocks``; 26 mysql> SELECT VARIABLE_VALUE FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'innodb_deadlocks';
27 +----------------+27 +----------------+
28 | VARIABLE_VALUE |28 | VARIABLE_VALUE |
29 +----------------+29 +----------------+
@@ -36,7 +36,7 @@
36Version Specific Information36Version Specific Information
37============================37============================
3838
39 * 5.1.47-11.0:39 * 5.5.8-20.0:
40 Full functionality available.40 Full functionality available.
4141
42Status Variables42Status Variables
4343
=== modified file 'doc/source/diagnostics/mysql_syslog.rst'
--- doc/source/diagnostics/mysql_syslog.rst 2011-10-07 23:38:41 +0000
+++ doc/source/diagnostics/mysql_syslog.rst 2012-02-13 08:57:19 +0000
@@ -26,6 +26,7 @@
2626
27 :cli: Yes27 :cli: Yes
28 :conf: Yes28 :conf: Yes
29 :server: No
29 :scope: Global30 :scope: Global
30 :dyn: Yes31 :dyn: Yes
31 :vartype: Boolean32 :vartype: Boolean
3233
=== modified file 'doc/source/diagnostics/response_time_distribution.rst'
--- doc/source/diagnostics/response_time_distribution.rst 2011-10-07 23:38:41 +0000
+++ doc/source/diagnostics/response_time_distribution.rst 2012-02-13 08:57:19 +0000
@@ -193,21 +193,18 @@
193Version Specific Information193Version Specific Information
194============================194============================
195195
196 * 5.1.49-12.0:196 * 5.5.8-20.0:
197 Full functionality available.197 Introduced variable variable:`have_response_time_distribution`.
198198
199 * 5.1.53-12.4:199 * 5.5.8-20.0:
200 Introduced have_response_time_distribution.200 Introduced variable variable:`query_response_time_stats`.
201
202 * 5.5.8-20.0:
203 Renamed variable :variable:`enable_query_response_time_stats` to :variable:`query_response_time_stats`.
204201
205System Variables202System Variables
206================203================
207204
208.. variable:: have_response_time_distribution205.. variable:: have_response_time_distribution
209206
210 :version 5.1.53-12.4: Introduced.207 :version 5.5.8-20.0: Introduced.
211 :scope: Global208 :scope: Global
212 :dyn: No209 :dyn: No
213 :vartype: Boolean210 :vartype: Boolean
214211
=== modified file 'doc/source/diagnostics/show_engines.rst'
--- doc/source/diagnostics/show_engines.rst 2011-10-07 23:38:41 +0000
+++ doc/source/diagnostics/show_engines.rst 2012-02-13 08:57:19 +0000
@@ -29,7 +29,7 @@
29Version-Specific Information29Version-Specific Information
30============================30============================
3131
32 * 5.1.49-12.0:32 * 5.5.8-20.0:
33 Full functionality available.33 Full functionality available.
3434
35Other Information35Other Information
3636
=== modified file 'doc/source/feature_comparison.rst'
--- doc/source/feature_comparison.rst 2011-09-20 07:03:00 +0000
+++ doc/source/feature_comparison.rst 2012-02-13 08:57:19 +0000
@@ -20,65 +20,132 @@
2020
21We provide these benefits by significantly enhancing |Percona Server| as compared to the standard |MySQL| database server:21We provide these benefits by significantly enhancing |Percona Server| as compared to the standard |MySQL| database server:
2222
23.. raw:: html23+---------------------------------------+----------------------+--------------+
2424|Features |Percona Server 5.5.20 |MySQL 5.5.20 |
25 <table class="datatable">25+=======================================+======================+==============+
26 <tr><th class="label">Feature</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr> 26|Open source | Yes | Yes |
27 <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>27+---------------------------------------+----------------------+--------------+
28 <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>28|ACID Compliance | Yes | Yes |
29 <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>29+---------------------------------------+----------------------+--------------+
30 <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>30|Multi-Version Concurrency Control | Yes | Yes |
31 <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>31+---------------------------------------+----------------------+--------------+
32 <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>32|Row-Level Locking | Yes | Yes |
33 <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>33+---------------------------------------+----------------------+--------------+
34 <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>34|Automatic Crash Recovery | Yes | Yes |
35 <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>35+---------------------------------------+----------------------+--------------+
36 <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>36|Table Partitioning | Yes | Yes |
37 <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>37+---------------------------------------+----------------------+--------------+
38 <tr><th class="label">Extra Features for Developers</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr>38|Views | Yes | Yes |
39 <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>39+---------------------------------------+----------------------+--------------+
40 <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>40|Subqueries | Yes | Yes |
41 <tr><th class="label">Extra Diagnostic Features</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr>41+---------------------------------------+----------------------+--------------+
42 <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>42|Triggers | Yes | Yes |
43 <tr><td class="label">INFORMATION_SCHEMA Tables</td><td>60</td><td>37</td></tr>43+---------------------------------------+----------------------+--------------+
44 <tr><td class="label">Global Performance and Status Counters</td><td>366</td><td>308</td></tr>44|Stored Procedures | Yes | Yes |
45 <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>45+---------------------------------------+----------------------+--------------+
46 <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>46|Foreign Keys | Yes | Yes |
47 <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>47+---------------------------------------+----------------------+--------------+
48 <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>48
49 <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>49+---------------------------------------+----------------------+--------------+
50 <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>50|Extra Features for Developers |Percona Server 5.5.20 |MySQL 5.5.20 |
51 <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>51+=======================================+======================+==============+
52 <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>52|NoSQL Socket-Level Interface | Yes | |
53 <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>53+---------------------------------------+----------------------+--------------+
54 <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>54|Extra Hash/Digest Functions | Yes | |
55 <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>55+---------------------------------------+----------------------+--------------+
56 <tr><th class="label">Durability and Reliability Enhancements</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr>56
57 <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>57+---------------------------------------+----------------------+--------------+
58 <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>58|Extra Diagnostic Features |Percona Server 5.5.20 |MySQL 5.5.20 |
59 <tr><th class="label">Performance &amp; Scalability Enhancements</th><th>Percona Server 5.5.8</th><th>MySQL 5.5.8</th></tr>59+=======================================+======================+==============+
60 <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>60|INFORMATION_SCHEMA Tables | 60 | 37 |
61 <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>61+---------------------------------------+----------------------+--------------+
62 <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>62|Global Performance and Status Counters | 370 | 310 |
63 <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>63+---------------------------------------+----------------------+--------------+
64 <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>64|Per-Table Performance Counters | Yes | |
65 <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>65+---------------------------------------+----------------------+--------------+
66 <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>66|Per-Index Performance Counters | Yes | |
67 <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>67+---------------------------------------+----------------------+--------------+
68 <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>68|Per-User Performance Counters | Yes | |
69 <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>69+---------------------------------------+----------------------+--------------+
70 <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>70|Per-Client Performance Counters | Yes | |
71 <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>71+---------------------------------------+----------------------+--------------+
72 <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> 72|Per-Thread Performance Counters | Yes | |
73 <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>73+---------------------------------------+----------------------+--------------+
74 <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>74|High-Resolution Process List Timing | Yes | |
75 <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>75+---------------------------------------+----------------------+--------------+
76 <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>76|Detailed Query Execution and Plan Log | Yes | |
77 <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>77+---------------------------------------+----------------------+--------------+
78 <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>78|Global Query Response Time Statistics | Yes | |
79 <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>79+---------------------------------------+----------------------+--------------+
80 <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>80|InnoDB Data Dictionary as I_S Tables | Yes | |
81 <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>81+---------------------------------------+----------------------+--------------+
82 <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>82|Access to InnoDB Data Statistics | Yes | |
83 </table>83+---------------------------------------+----------------------+--------------+
84|Enhanced SHOW INNODB STATUS | Yes | |
85+---------------------------------------+----------------------+--------------+
86|Enhanced Mutex Diagnostics | Yes | |
87+---------------------------------------+----------------------+--------------+
88
89+---------------------------------------+----------------------+--------------+
90|Durability and Reliability Enhancements|Percona Server 5.5.20 |MySQL 5.5.20 |
91+=======================================+======================+==============+
92|Transactional Replication State | Yes | |
93+---------------------------------------+----------------------+--------------+
94|Handles Corrupted Tables Gracefully | Yes | |
95+---------------------------------------+----------------------+--------------+
96
97+---------------------------------------+----------------------+--------------+
98|Performance & Scalability Enhancements |Percona Server 5.5.20 |MySQL 5.5.20 |
99+=======================================+======================+==============+
100|Support for Multiple I/O Threads | Yes | Yes |
101+---------------------------------------+----------------------+--------------+
102|Dedicated Purge Threads | Yes | Yes |
103+---------------------------------------+----------------------+--------------+
104|Self-Tuning Checkpoint Algorithm | Yes | |
105+---------------------------------------+----------------------+--------------+
106|Fine-Grained Mutex Locking | Yes | |
107+---------------------------------------+----------------------+--------------+
108|Lock-Free Algorithms | Yes | |
109+---------------------------------------+----------------------+--------------+
110|Improved MEMORY Storage Engine | Yes | |
111+---------------------------------------+----------------------+--------------+
112|Partitioned Adaptive Hash Search | Yes | |
113+---------------------------------------+----------------------+--------------+
114|Separate Doublewrite File | Yes | |
115+---------------------------------------+----------------------+--------------+
116|Fast Checksum Algorithm | Yes | |
117+---------------------------------------+----------------------+--------------+
118|Buffer Pool Pre-Load | Yes | |
119+---------------------------------------+----------------------+--------------+
120|Fast Shut-Down | Yes | |
121+---------------------------------------+----------------------+--------------+
122|Background Table Drop | Yes | |
123+---------------------------------------+----------------------+--------------+
124|Support for FlashCache | Yes | |
125+---------------------------------------+----------------------+--------------+
126|Read-Ahead Improvements | Yes | |
127+---------------------------------------+----------------------+--------------+
128
129+---------------------------------------+----------------------+--------------+
130|Extra Features for DBA/Operations Staff|Percona Server 5.5.20 |MySQL 5.5.20 |
131+=======================================+======================+==============+
132|Configurable Page Sizes | Yes | |
133+---------------------------------------+----------------------+--------------+
134|Import Tables From Different Servers | Yes | |
135+---------------------------------------+----------------------+--------------+
136|Configurable Data Dictionary Size | Yes | |
137+---------------------------------------+----------------------+--------------+
138|Configurable Insert Buffer Size | Yes | |
139+---------------------------------------+----------------------+--------------+
140|Active Change Buffer Purging | Yes | |
141+---------------------------------------+----------------------+--------------+
142|Error/Warning Logging Enhancements | Yes | |
143+---------------------------------------+----------------------+--------------+
144|Configurable Fast Index Creation | Yes | |
145+---------------------------------------+----------------------+--------------+
146|Fast Index Renaming | Yes | |
147+---------------------------------------+----------------------+--------------+
148|Support for Fake Changes | Yes | |
149+---------------------------------------+----------------------+--------------+
150
84151
85152
=== modified file 'doc/source/flexibility/buff_read_ahead_area.rst'
--- doc/source/flexibility/buff_read_ahead_area.rst 2011-10-07 23:38:41 +0000
+++ doc/source/flexibility/buff_read_ahead_area.rst 2012-02-13 08:57:19 +0000
@@ -18,7 +18,7 @@
18Version Specific Information18Version Specific Information
19============================19============================
2020
21 * :rn:`5.1.47-12.0` :21 * :rn:`5.5.8-20.0` :
22 Full functionality available.22 Full functionality available.
2323
24Other Information24Other Information
2525
=== modified file 'doc/source/flexibility/innodb_fast_shutdown.rst'
--- doc/source/flexibility/innodb_fast_shutdown.rst 2011-10-07 23:38:41 +0000
+++ doc/source/flexibility/innodb_fast_shutdown.rst 2012-02-13 08:57:19 +0000
@@ -15,7 +15,7 @@
15Version Specific Information15Version Specific Information
16============================16============================
1717
18 * 5.1.52-12.3:18 * 5.5.8-20
19 Full functionality available.19 Full functionality available.
2020
21Other Information21Other Information
2222
=== modified file 'doc/source/flexibility/log_warnings_suppress.rst'
--- doc/source/flexibility/log_warnings_suppress.rst 2011-10-07 23:38:41 +0000
+++ doc/source/flexibility/log_warnings_suppress.rst 2012-02-13 08:57:19 +0000
@@ -10,44 +10,12 @@
10Version Specific Information10Version Specific Information
11============================11============================
1212
13 * 5.1.47-11.0:
14 System variable :variable:`suppress_log_warning_1592` introduced.
15
16 * 5.5.8-20.0:13 * 5.5.8-20.0:
17 System variable :variable:`suppress_log_warning_1592` replaced by :variable:`log_warnings_silence`.14 System variable :variable:`log_warnings_silence` introduced.
1815
19 * 5.5.10-20.1:16 * 5.5.10-20.1:
20 Renamed variable :variable:`log_warnings_silence` to :variable:`log_warnings_suppress`.17 Renamed variable :variable:`log_warnings_silence` to :variable:`log_warnings_suppress`.
2118
22System Variables
23================
24
25.. variable:: suppress_log_warning_1592
26
27 :version 5.1.47-11.0: Introduced.
28 :version 5.5.8-20.0: Deleted.
29 :cli: Yes
30 :conf: Yes
31 :scope: Global
32 :dyn: Yes
33 :vartype: Boolean
34 :default: OFF
35 :range: ON(='1592') / OFF
36
37This 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.
38
39**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.
40
41When ``ON``, disables reporting of warning #1592 (unsafe statement for binary logging).
42
43All 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.
44
45In some circumstances, |MySQL| will warn you that a statement is unsafe to replicate even though it is perfectly safe. For example: ::
46
47 090213 16:58:54 [Warning] Statement is not safe to log in statement format.
48
49This 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.
50
51.. variable:: log_warnings_suppress19.. variable:: log_warnings_suppress
5220
53 :version 5.5.8-20.0: Introduced.21 :version 5.5.8-20.0: Introduced.
5422
=== modified file 'doc/source/flexibility/mysql_remove_eol_carret.rst'
--- doc/source/flexibility/mysql_remove_eol_carret.rst 2011-10-07 23:38:41 +0000
+++ doc/source/flexibility/mysql_remove_eol_carret.rst 2012-02-13 08:57:19 +0000
@@ -14,7 +14,7 @@
14Version Specific Information14Version Specific Information
15============================15============================
1616
17 * 5.1.50-12.1:17 * 5.5.8-20.0:
18 Full functionality.18 Full functionality.
1919
20Client Command Line Parameter20Client Command Line Parameter
2121
=== removed file 'doc/source/flexibility/replication_skip_single_statement.rst'
--- doc/source/flexibility/replication_skip_single_statement.rst 2011-10-07 23:38:41 +0000
+++ doc/source/flexibility/replication_skip_single_statement.rst 1970-01-01 00:00:00 +0000
@@ -1,167 +0,0 @@
1.. _replication_skip_single_statement:
2
3===========================
4 Replication Stop Recovery
5===========================
6
7After 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.
8
9The 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>`_:
10
11When using this statement, it is important to understand that the binary log is actually organized
12as a sequence of groups known as event groups. Each event group consists of a sequence of events.
13
14 * For transactional tables, an event group corresponds to a transaction.
15
16 * For nontransactional tables, an event group corresponds to a single SQL statement.
17
18A single transaction can contain changes to both transactional and nontransactional tables.
19
20When 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.
21
22When 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.
23
24
25Version Specific Information
26============================
27
28 * 5.1.49-12.0:
29 Full functionality released.
30
31System Variables
32================
33
34The following status variable was introduced by this feature.
35
36.. variable:: sql_slave_statement_skip_counter
37
38 :cli: Yes
39 :conf: Yes
40 :scope: Global
41 :dyn: Yes
42 :vartype: Numeric
43 :default: 0
44 :range: 1-MAXLONGINT
45
46This variable specifies the number of events in the current event group to skip.
47
48**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.
49
50Consider this case: ::
51
52 SET GLOBAL sql_slave_statement_skip_counter=n;
53 SET GLOBAL sql_slave__skip_counter=m;
54
55The 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**.
56
57Example
58=======
59
60In the example here, a master server with two slaves is assumed. A table is created on the master and then a replication error occurs.
61
62Then 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.
63
64Setup
65-----
66
67 - Prepare the master server: ::
68
69 DROP TABLE IF EXISTS t;
70 CREATE TABLE t(id INT UNIQUE PRIMARY KEY) ENGINE=|InnoDB|;
71 INSERT INTO t VALUES (1),(2);
72
73 - Prepare Slave #1 and Slave #2: ::
74
75 DROP TABLE IF EXISTS t;
76 CREATE TABLE t(id INT UNIQUE PRIMARY KEY) ENGINE=|InnoDB|;
77 INSERT INTO t VALUES (1),(2),(3),(5);
78
79 - Start replication of the master to the two slaves.
80
81Create the Replication Error
82----------------------------
83
84Run the following on the master: ::
85
86 START TRANSACTION;
87 INSERT INTO t VALUES (3);
88 INSERT INTO t VALUES (4);
89 COMMIT;
90
91Both slaves will fail with the following error: ::
92
93 Error ``Duplicate entry ``3`` for key ``PRIMARY```` on query. Default database: ``test``. Query: ``INSERT INTO t VALUES (3)``
94
95Repair the Replication Error
96----------------------------
97
98Now, 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.
99
100Slave Repair Using sql_slave_skip_counter
101~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
102
103To repair either slave, do the following: ::
104
105 SET GLOBAL sql_slave_skip_counter=1;
106 START SLAVE;
107
108This will cause the slave to skip the following statement: ::
109
110 INSERT INTO t VALUES (3);
111
112In 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: ::
113
114 INSERT INTO t VALUES (4);
115 COMMIT;
116
117Now run the following on the slave: ::
118
119 SELECT * FROM t;
120
121This will give the result: ::
122
123 id
124 1
125 2
126 3
127 5
128
129Since the table's original contents are unchanged, this shows that ``sql_slave_skip_counter`` caused the entire event group to be skipped.
130
131Slave Repair Using sql_slave_statement_skip_counter
132~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
133
134To repair either slave, do the following: ::
135
136 SET GLOBAL sql_slave_statement_skip_counter=1;
137 START SLAVE;
138
139This will cause the slave to skip the following statement: ::
140
141 INSERT INTO t VALUES (3);
142
143However, 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: ::
144
145 INSERT INTO t VALUES (4);
146 COMMIT;
147
148Now, we can see the difference in results when we run: ::
149
150 SELECT * FROM t;
151
152Now, our results are: ::
153
154 id
155 1
156 2
157 3
158 4
159 5
160
161In 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.
162
163
164Other Reading
165-------------
166
167 * `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>`_
1680
=== modified file 'doc/source/index.rst'
--- doc/source/index.rst 2012-02-03 10:23:20 +0000
+++ doc/source/index.rst 2012-02-13 08:57:19 +0000
@@ -88,7 +88,6 @@
88 flexibility/innodb_files_extend88 flexibility/innodb_files_extend
89 flexibility/log_warnings_suppress89 flexibility/log_warnings_suppress
90 flexibility/mysql_remove_eol_carret90 flexibility/mysql_remove_eol_carret
91 flexibility/replication_skip_single_statement
92 flexibility/buff_read_ahead_area91 flexibility/buff_read_ahead_area
93 flexibility/innodb_fast_shutdown92 flexibility/innodb_fast_shutdown
94 flexibility/improved_memory_engine93 flexibility/improved_memory_engine
@@ -119,7 +118,6 @@
119 management/innodb_lru_dump_restore118 management/innodb_lru_dump_restore
120 management/innodb_fast_index_creation119 management/innodb_fast_index_creation
121 management/innodb_extended_fast_index_creation120 management/innodb_extended_fast_index_creation
122 management/innodb_fast_index_renaming
123 management/sql_no_fcache121 management/sql_no_fcache
124 management/udf_maatkit122 management/udf_maatkit
125 management/innodb_fake_changes123 management/innodb_fake_changes
126124
=== modified file 'doc/source/management/innodb_fast_index_creation.rst'
--- doc/source/management/innodb_fast_index_creation.rst 2011-10-07 23:38:41 +0000
+++ doc/source/management/innodb_fast_index_creation.rst 2012-02-13 08:57:19 +0000
@@ -44,10 +44,10 @@
44Version Specific Information44Version Specific Information
45============================45============================
4646
47 * 5.1.49-12.0: 47 * 5.5.8-20.0:
48 Variable :variable:`fast_index_creation` implemented.48 Variable :variable:`fast_index_creation` implemented.
4949
50 * 5.1.56-12.7, 5.5.11-21.2:50 * 5.5.11-21.2:
51 Expanded the applicability of fast index creation to :command:`mysqldump`, ``ALTER TABLE``, and ``OPTIMIZE TABLE``.51 Expanded the applicability of fast index creation to :command:`mysqldump`, ``ALTER TABLE``, and ``OPTIMIZE TABLE``.
5252
5353
5454
=== removed file 'doc/source/management/innodb_fast_index_renaming.rst'
--- doc/source/management/innodb_fast_index_renaming.rst 2011-10-07 23:38:41 +0000
+++ doc/source/management/innodb_fast_index_renaming.rst 1970-01-01 00:00:00 +0000
@@ -1,38 +0,0 @@
1.. _innodb_fast_index_renaming:
2
3=====================
4 Fast Index Renaming
5=====================
6
7This 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: ::
8
9 ALTER TABLE ... RENAME INDEX xxx TO yyy;
10
11Several limitations exist:
12
13 * 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.
14
15 * 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'``.
16
17 * Use of a partitioned table is not allowed. If ``ALTER TABLE`` is applied to a partitioned table, an error will occur.
18
19 * 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.
20
21Errors 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.
22
23An internally reserved InnoDB name (e.g., ``GEN_CLUST_INDEX``) cannot be used as an index name. If one is, an error is reported.
24
25If 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.
26
27
28Version Specific Information
29============================
30
31 * 5.1.49-12.0:
32 Not yet released externally
33
34Error Codes
35===========
36
37 * ``error_er_wrong_usage``:
38 Incorrect usage of %s and %s
390
=== modified file 'doc/source/management/innodb_lru_dump_restore.rst'
--- doc/source/management/innodb_lru_dump_restore.rst 2011-10-07 23:38:41 +0000
+++ doc/source/management/innodb_lru_dump_restore.rst 2012-02-13 08:57:19 +0000
@@ -105,7 +105,7 @@
105Version Specific Information105Version Specific Information
106============================106============================
107107
108 * 5.1.50-12.1:108 * 5.5.8-20.0:
109 Automatic dump/restore implemented.109 Automatic dump/restore implemented.
110 * 5.5.10-20.1:110 * 5.5.10-20.1:
111 Renamed variable :variable:`innodb_auto_lru_dump` to :variable:`innodb_buffer_pool_restore_at_startup`.111 Renamed variable :variable:`innodb_auto_lru_dump` to :variable:`innodb_buffer_pool_restore_at_startup`.
112112
=== modified file 'doc/source/management/sql_no_fcache.rst'
--- doc/source/management/sql_no_fcache.rst 2011-10-07 23:38:41 +0000
+++ doc/source/management/sql_no_fcache.rst 2012-02-13 08:57:19 +0000
@@ -18,7 +18,7 @@
18Version-Specific Information18Version-Specific Information
19============================19============================
2020
21 * 5.1.49-12.0:21 * 5.5.8-20.0:
22 Full functionality available.22 Full functionality available.
2323
24Other Information24Other Information
2525
=== modified file 'doc/source/performance/handlersocket.rst'
--- doc/source/performance/handlersocket.rst 2011-10-07 23:38:41 +0000
+++ doc/source/performance/handlersocket.rst 2012-02-13 08:57:19 +0000
@@ -19,7 +19,7 @@
19Version Specific Information19Version Specific Information
20============================20============================
2121
22 * 5.1.52-12.322 * 5.5.11-20.2
23 Full functionality available.23 Full functionality available.
2424
25Other Information25Other Information
2626
=== modified file 'doc/source/performance/innodb_doublewrite_path.rst'
--- doc/source/performance/innodb_doublewrite_path.rst 2011-10-07 23:38:41 +0000
+++ doc/source/performance/innodb_doublewrite_path.rst 2012-02-13 08:57:19 +0000
@@ -50,17 +50,12 @@
5050
51Basically 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.51Basically 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.
5252
53Prior 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.
54
55
56Version Specific Information53Version Specific Information
57============================54============================
5855
59 * 5.1.47-11.0 56 * 5.5.8-20.0
60 Full functionality available.57 Full functionality available.
6158
62 * 5.1.53-12.4
63 Rebuild of database and system files no longer necessary.
6459
65System Variables60System Variables
66================61================
6762
=== modified file 'doc/source/reliability/error_pad.rst'
--- doc/source/reliability/error_pad.rst 2011-10-07 23:38:41 +0000
+++ doc/source/reliability/error_pad.rst 2012-02-13 08:57:19 +0000
@@ -51,5 +51,5 @@
51Version-Specific Information51Version-Specific Information
52============================52============================
5353
54 * 5.1.49-12.0:54 * 5.5.8-20.0
55 Full functionality available.55 Full functionality available.
5656
=== modified file 'doc/source/reliability/log_connection_error.rst'
--- doc/source/reliability/log_connection_error.rst 2011-10-07 23:38:41 +0000
+++ doc/source/reliability/log_connection_error.rst 2012-02-13 08:57:19 +0000
@@ -10,5 +10,5 @@
10Version-Specific Information10Version-Specific Information
11============================11============================
1212
13 * 5.1.49-12.0:13 * 5.5.8-20.0:
14 Full functionality available.14 Full functionality available.
1515
=== modified file 'doc/source/reliability/show_slave_status_nolock.rst'
--- doc/source/reliability/show_slave_status_nolock.rst 2011-10-07 23:38:41 +0000
+++ doc/source/reliability/show_slave_status_nolock.rst 2012-02-13 08:57:19 +0000
@@ -20,5 +20,4 @@
20Version Specific Information20Version Specific Information
21============================21============================
2222
23 * 5.1.52-12.3:23 * 5.5.8-20.0:
24 Currently only the source code is distributed; the feature is not included in binaries.

Subscribers

People subscribed via source and target branches