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

[Hrvoje Matijakovic]

[Stewart Smith (stewart)]

review: Approve

=== modified file 'doc/source/development.rst'
--- doc/source/development.rst	2012-01-27 11:37:42 +0000
+++ doc/source/development.rst	2012-12-13 13:30:28 +0000
@@ -19,7 +19,7 @@
 
 Overview
 ~~~~~~~~
-At Percona we use `Bazaar <http://www.bazaar-vcs.org>`_ for source
+At Percona we use `Bazaar <http://bazaar.canonical.com/en/>`_ for source
 control and `launchpad <http://www.launchpad.net>`_ for both
 code hosting and release management.
 
@@ -205,7 +205,7 @@
 Percona Xtrabackup
 ~~~~~~~~~~~~~~~~~~
 
-`<http://jenkins.percona.com/view/Percona%20Xtrabackup/>`_
+`<http://jenkins.percona.com/view/XtraBackup/>`_
 
 We currently build both xtrabackup 1.6 and xtrabackup trunk (will become 1.7).
 
@@ -221,14 +221,14 @@
 Percona Server 5.1
 ------------------
 
-`<http://jenkins.percona.com/view/Percona%20Server%205.1/>`_
+`<http://jenkins.percona.com/view/PS%205.1/>`_
 
 We have trunk and param jobs. We also have a valgrind job that will run after a successful trunk build.
 
 Percona Server 5.5
 ------------------
 
-`<http://jenkins.percona.com/view/Percona%20Server%205.5/>`_
+`<http://jenkins.percona.com/view/PS%205.5/>`_
 
 Similar to 5.1, but for PS5.5 instead.
 
 
=== modified file 'doc/source/diagnostics/innodb_deadlock_count.rst'
--- doc/source/diagnostics/innodb_deadlock_count.rst	2011-10-07 00:55:06 +0000
+++ doc/source/diagnostics/innodb_deadlock_count.rst	2012-12-13 13:30:28 +0000
@@ -36,7 +36,7 @@
 Version Specific Information
 ============================
 
-  * 5.1.47-11.0:
+  * :rn:`5.1.47-rel11.1`:
     Full functionality available.
 
 Status Variables
 
=== modified file 'doc/source/diagnostics/mysql_syslog.rst'
--- doc/source/diagnostics/mysql_syslog.rst	2012-05-29 18:31:23 +0000
+++ doc/source/diagnostics/mysql_syslog.rst	2012-12-13 13:30:28 +0000
@@ -10,7 +10,7 @@
 Version Specific Information
 ============================
 
-  * 5.1.49-12.0:
+  * :rn:`5.1.49-rel12.0`:
     Full functionality available.
 
 Other Information
 
=== modified file 'doc/source/diagnostics/process_list.rst'
--- doc/source/diagnostics/process_list.rst	2011-10-07 00:55:06 +0000
+++ doc/source/diagnostics/process_list.rst	2012-12-13 13:30:28 +0000
@@ -6,29 +6,6 @@
 
 This page describes Percona changes to both the standard |MySQL| ``SHOW PROCESSLIST`` command and the standard |MySQL| ``INFORMATION_SCHEMA`` table ``PROCESSLIST``.
 
-The changes that have been made as of version 5.5 of the server are:
-
-  * ``SHOW PROCESSLIST`` command:
-
-    * added columns ``ROWS_EXAMINED``, ``ROWS_SENT``, and ``ROWS_READ``
-
-  * ``PROCESSLIST`` table:
-
-    * added columns ``TIME_MS``, ``ROWS_EXAMINED``, ``ROWS_SENT``, and ``ROWS_READ``
-
-Version Specific Information
-============================
-
-  * 5.0.91-22:
-
-    * Added column ``TIME_MS`` to table ``PROCESSLIST``.
-
-  * 5.5.10-20.1:
-
-    * Added columns ``ROWS_EXAMINED``, ``ROWS_SENT``, and ``ROWS_READ`` to ``SHOW PROCESSLIST`` command.
-
-    * Added columns ``ROWS_EXAMINED``, ``ROWS_SENT``, and ``ROWS_READ`` to table ``PROCESSLIST``.
-
 INFORMATION_SCHEMA Tables
 =========================
 
@@ -48,8 +25,6 @@
    :column ROWS_EXAMINED: The number of rows examined by the statement being executed.
    :column ROWS_SENT:	The number of rows sent by the statement being executed.
    :column ROWS_READ: The number of rows read by the statement being executed.
-   :version 5.0.91-22: Added column ``TIME_MS``
-   :version 5.5.10-20.1: Added columns ``ROWS_EXAMINED``, ``ROWS_SENT``, and ``ROWS_READ``
 
 
 Example Output
 
=== modified file 'doc/source/diagnostics/response_time_distribution.rst'
--- doc/source/diagnostics/response_time_distribution.rst	2012-12-10 14:01:11 +0000
+++ doc/source/diagnostics/response_time_distribution.rst	2012-12-13 13:30:28 +0000
@@ -193,10 +193,10 @@
 Version Specific Information
 ============================
 
-  * 5.1.49-12.0:
+  * :rn:`5.1.49-rel12.0`:
     Full functionality available.
 
-  * 5.1.53-12.4:
+  * :rn:`5.1.53-12.4`:
     Introduced :variable:`have_response_time_distribution`.
 
 System Variables
@@ -232,7 +232,7 @@
 
 .. variable:: enable_query_response_time_stats
 
-     :version 5.1.49-12.0: Introduced.
+     :version 5.1.49-rel12.0: Introduced.
      :cli: Yes
      :conf: Yes
      :scope: Global
 
=== modified file 'doc/source/diagnostics/show_engines.rst'
--- doc/source/diagnostics/show_engines.rst	2011-10-07 00:55:06 +0000
+++ doc/source/diagnostics/show_engines.rst	2012-12-13 13:30:28 +0000
@@ -29,7 +29,7 @@
 Version-Specific Information
 ============================
 
-  * 5.1.49-12.0:
+  * :rn:`5.1.49-rel12.0`:
     Full functionality available.
 
 Other Information
 
=== modified file 'doc/source/diagnostics/slow_extended.rst'
--- doc/source/diagnostics/slow_extended.rst	2012-09-17 07:36:57 +0000
+++ doc/source/diagnostics/slow_extended.rst	2012-12-13 13:30:28 +0000
@@ -8,20 +8,12 @@
 
 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|.
 
-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.
+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.
 
 
 Version Specific Information
 ============================
 
-  * ``4.1.x``:
-
-    * Limited functionality available: only microsecond resolution, no added statistics.
-
-  * ``5.0.x``:
-
-    * Full functionality available.
-
   * ``5.1.x``:
 
     * Microsecond resolution included in official |MySQL| server; this feature adds statistics.
@@ -34,7 +26,7 @@
 
     * Full functionality of :variable:`use_global_log_slow_control` available.
 
-    * Fixed :bug:`600684` - :variable:`log_slow_verbosity` ``=iInnodb`` doesn't work on slave (statement-based replication)
+    * Fixed :bug:`600684` - :variable:`log_slow_verbosity` ``=Innodb`` doesn't work on slave (statement-based replication)
 
   * :rn:`5.1.53-11.7`:
 
@@ -134,16 +126,12 @@
 
 If ``TRUE``, a timestamp is printed on every slow log record. Multiple records may have the same time.
 
-**NOTE:** This variable has been renamed to :variable:`slow_query_log_timestamp_always` since :rn:`5.5.10-20.1`.
-
-
 .. variable:: log_slow_verbosity
 
      :cli: Yes
      :conf: Yes
      :scope: Global, session
      :dyn: Yes
-     :version 5.5.8-20.0: Added ``profiling`` and ``profiling_use_getrusage``
 
 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:
 
 
=== modified file 'doc/source/flexibility/buff_read_ahead_area.rst'
--- doc/source/flexibility/buff_read_ahead_area.rst	2012-06-13 10:52:23 +0000
+++ doc/source/flexibility/buff_read_ahead_area.rst	2012-12-13 13:30:28 +0000
@@ -18,7 +18,7 @@
 Version Specific Information
 ============================
 
-  * :rn:`5.1.47-12.0` :
+  * :rn:`5.1.49-rel12.0` :
     Full functionality available.
 
 Other Information
 
=== modified file 'doc/source/flexibility/innodb_fast_shutdown.rst'
--- doc/source/flexibility/innodb_fast_shutdown.rst	2011-10-07 00:55:06 +0000
+++ doc/source/flexibility/innodb_fast_shutdown.rst	2012-12-13 13:30:28 +0000
@@ -15,7 +15,7 @@
 Version Specific Information
 ============================
 
-  * 5.1.52-12.3:
+  * :rn:`5.1.52-12.3`
     Full functionality available.
 
 Other Information
 
=== modified file 'doc/source/flexibility/log_warnings_suppress.rst'
--- doc/source/flexibility/log_warnings_suppress.rst	2011-10-07 00:55:06 +0000
+++ doc/source/flexibility/log_warnings_suppress.rst	2012-12-13 13:30:28 +0000
@@ -10,22 +10,15 @@
 Version Specific Information
 ============================
 
-  * 5.1.47-11.0: 
+  * :rn:`5.1.47-rel11.1`
     System variable :variable:`suppress_log_warning_1592` introduced.
 
-  * 5.5.8-20.0:
-    System variable :variable:`suppress_log_warning_1592` replaced by :variable:`log_warnings_silence`.
-
-  * 5.5.10-20.1:
-    Renamed variable :variable:`log_warnings_silence` to :variable:`log_warnings_suppress`.
-
 System Variables
 ================
 
 .. variable:: suppress_log_warning_1592
 
-     :version 5.1.47-11.0: Introduced.
-     :version 5.5.8-20.0: Deleted.
+     :version 5.1.47-rel11.1: Introduced.
      :cli: Yes
      :conf: Yes
      :scope: Global
@@ -46,33 +39,10 @@
 
   090213 16:58:54 [Warning] Statement is not safe to log in statement format.
 
-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`.
-
-.. variable:: log_warnings_suppress
-
-     :version 5.5.8-20.0: Introduced.
-     :version 5.5.10-20.1: Renamed.
-     :cli: Yes
-     :conf: Yes
-     :scope: Global
-     :dyn: Yes
-     :vartype: SET
-     :default: ``(empty string)``
-     :range: ``(empty string)``, ``1592``
-
-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.
-
-It is intended to provide a more general mechanism for disabling warnings than existed previously with variable suppress_log_warning_1592.
-
-When set to the empty string, no warnings are disabled. When set to ``1592``, warning #1592 messages (unsafe statement for binary logging) are suppressed.
-
-In the future, the ability to optionally disable additional warnings may also be added.
-
-
 Related Reading
 ===============
 
-  * `MySQL bug 42851 <http://bugs.mysql.com/bug.php?id=42851>`_
+  * `MySQL bug #42851 <http://bugs.mysql.com/bug.php?id=42851>`_
 
   * `MySQL InnoDB replication <http://dev.mysql.com/doc/refman/5.1/en/innodb-and-mysql-replication.html>`_
 
 
=== modified file 'doc/source/flexibility/mysql_remove_eol_carret.rst'
--- doc/source/flexibility/mysql_remove_eol_carret.rst	2011-10-07 00:55:06 +0000
+++ doc/source/flexibility/mysql_remove_eol_carret.rst	2012-12-13 13:30:28 +0000
@@ -14,7 +14,7 @@
 Version Specific Information
 ============================
 
-  * 5.1.50-12.1:
+  * :rn:`5.1.50-rel12.1`
     Full functionality.
 
 Client Command Line Parameter
 
=== modified file 'doc/source/flexibility/mysqlbinlog_change_db.rst'
--- doc/source/flexibility/mysqlbinlog_change_db.rst	2012-05-17 11:21:21 +0000
+++ doc/source/flexibility/mysqlbinlog_change_db.rst	2012-12-13 13:30:28 +0000
@@ -66,7 +66,7 @@
 Version Specific Information
 ============================
 
-  * 5.1.62-13.3
+  * :rn:`5.1.62-13.3`
     Full functionality.
 
 Client Command Line Parameter
 
=== modified file 'doc/source/flexibility/replication_skip_single_statement.rst'
--- doc/source/flexibility/replication_skip_single_statement.rst	2011-10-07 00:55:06 +0000
+++ doc/source/flexibility/replication_skip_single_statement.rst	2012-12-13 13:30:28 +0000
@@ -25,7 +25,7 @@
 Version Specific Information
 ============================
 
-  * 5.1.49-12.0:
+  * :rn:`5.1.49-rel12.0`
     Full functionality released.
 
 System Variables
 
=== modified file 'doc/source/index.rst'
--- doc/source/index.rst	2012-12-10 14:01:11 +0000
+++ doc/source/index.rst	2012-12-13 13:30:28 +0000
@@ -103,7 +103,7 @@
    reliability/log_connection_error
    reliability/error_pad
    reliability/innodb_corrupt_table_action
-   reliability/innodb_recovery_update_relay_log
+   reliability/crash_resistant_replication
    reliability/show_slave_status_nolock
 
 Management Improvements
@@ -120,7 +120,6 @@
    management/innodb_lru_dump_restore
    management/innodb_fast_index_creation
    management/innodb_extended_fast_index_creation
-   management/innodb_fast_index_renaming
    management/sql_no_fcache
    management/udf_maatkit
    management/innodb_fake_changes
 
=== modified file 'doc/source/installation.rst'
--- doc/source/installation.rst	2012-01-09 04:30:56 +0000
+++ doc/source/installation.rst	2012-12-13 13:30:28 +0000
@@ -170,7 +170,7 @@
  Installing |Percona Server| from the Bazaar Source Tree
 ========================================================
 
-Percona uses the `Bazaar <http://www.bazaar-vcs.org>`_ revision
+Percona uses the `Bazaar <http://bazaar.canonical.com/en/>`_ revision
 control system for development. To build the latest Percona Server
 from the source tree you will need Bazaar installed on your system.
 
 
=== modified file 'doc/source/management/changed_page_tracking.rst'
--- doc/source/management/changed_page_tracking.rst	2012-09-03 09:31:43 +0000
+++ doc/source/management/changed_page_tracking.rst	2012-12-13 13:30:28 +0000
@@ -35,7 +35,7 @@
 .. variable:: innodb_track_changed_pages
 
    :version 5.1.65-14.0: Variable introduced
-   :cli: No
+   :cli: Yes
    :conf: Yes
    :scope: Global
    :dyn: No
 
=== modified file 'doc/source/management/innodb_buffer_pool_shm.rst'
--- doc/source/management/innodb_buffer_pool_shm.rst	2011-10-07 00:55:06 +0000
+++ doc/source/management/innodb_buffer_pool_shm.rst	2012-12-13 13:30:28 +0000
@@ -17,12 +17,12 @@
 Version Specific Information
 ============================
 
-  * 5.1.49-12.0:
+  * :rn:`5.1.49-rel12.0`
     Feature introduced.
 
-  * 5.1.50-12.1:
+  * :rn:`5.1.50-rel12.1`
     System variable :variable:`innodb_buffer_pool_shm_checksum` added.
 
-  * 5.1.58-12.9:
+  * :rn:`5.1.58-12.9`
     Feature removed, as LRU Dump/Restore is less invasive, more
     reliable and a better solution.
 
=== modified file 'doc/source/management/innodb_expand_import.rst'
--- doc/source/management/innodb_expand_import.rst	2012-06-13 10:52:23 +0000
+++ doc/source/management/innodb_expand_import.rst	2012-12-13 13:30:28 +0000
@@ -74,15 +74,15 @@
 Version Specific Information
 ============================
 
-  * 5.5.10-20.1:
-    Renamed variable :variable:`innodb_expand_import` to :variable:`innodb_import_table_from_xtrabackup`.
+  * :rn:`5.1.50-rel12.1`
+    Introduced variable :variable:`innodb_expand_import`.
 
 System Variables
 ================
 
 .. variable:: innodb_expand_import
 
-     :version 5.5.10-20.1: Renamed.
+     :version 5.1.50-rel12.1: Introduced
      :cli: Yes
      :conf: Yes
      :scope: Global
@@ -93,25 +93,6 @@
 
 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).
 
- 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.
-
-
-.. variable:: innodb_import_table_from_xtrabackup
-
-     :version 5.5.10-20.1: Introduced.
-     :cli: Yes
-     :conf: Yes
-     :scope: Global
-     :dyn: Yes
-     :vartype: ULONG
-     :default: 0
-     :range: 0-1
-
-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).
-
- 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.
-
-
 .. Other Information
 
 
 
=== modified file 'doc/source/management/innodb_extended_fast_index_creation.rst'
--- doc/source/management/innodb_extended_fast_index_creation.rst	2012-01-30 16:43:47 +0000
+++ doc/source/management/innodb_extended_fast_index_creation.rst	2012-12-13 13:30:28 +0000
@@ -58,7 +58,7 @@
 Version Specific Information
 ============================
 
-  * 5.1.59-13.0 
+  * :rn:`5.1.59-13.0`:
     Variable :variable:`expand_fast_index_creation` implemented.
     This variable controls whether fast index creation optimizations made by Perocna are used.
 
 
=== modified file 'doc/source/management/innodb_fast_index_creation.rst'
--- doc/source/management/innodb_fast_index_creation.rst	2012-07-12 08:48:23 +0000
+++ doc/source/management/innodb_fast_index_creation.rst	2012-12-13 13:30:28 +0000
@@ -23,10 +23,10 @@
 Version Specific Information
 ============================
 
-  * 5.1.49-12.0: 
+  * :rn:`5.1.49-rel12.0`: 
     Variable :variable:`fast_index_creation` implemented.
 
-  * 5.1.56-12.7, 5.5.11-21.2:
+  * :rn:`5.1.56-12.7`:
     Expanded the applicability of fast index creation to :command:`mysqldump`, ``ALTER TABLE``, and ``OPTIMIZE TABLE``.
 
 
 
=== removed file 'doc/source/management/innodb_fast_index_renaming.rst'
--- doc/source/management/innodb_fast_index_renaming.rst	2011-10-07 00:55:06 +0000
+++ doc/source/management/innodb_fast_index_renaming.rst	1970-01-01 00:00:00 +0000
@@ -1,38 +0,0 @@
-.. _innodb_fast_index_renaming:
-
-=====================
- Fast Index Renaming
-=====================
-
-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: ::
-
-  ALTER TABLE ... RENAME INDEX xxx TO yyy;
-
-Several limitations exist:
-
-  * 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.
-
-  * 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'``.
-
-  * Use of a partitioned table is not allowed. If ``ALTER TABLE`` is applied to a partitioned table, an error will occur.
-
-  * 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.
-
-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.
-
-An internally reserved InnoDB name (e.g., ``GEN_CLUST_INDEX``) cannot be used as an index name. If one is, an error is reported.
-
-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.
-
-
-Version Specific Information
-============================
-
-  * 5.1.49-12.0:
-    Not yet released externally
-
-Error Codes
-===========
-
-  * ``error_er_wrong_usage``:
-    Incorrect usage of %s and %s
 
=== modified file 'doc/source/management/innodb_lru_dump_restore.rst'
--- doc/source/management/innodb_lru_dump_restore.rst	2012-12-10 14:01:11 +0000
+++ doc/source/management/innodb_lru_dump_restore.rst	2012-12-13 13:30:28 +0000
@@ -15,7 +15,7 @@
 Automatic Operation
 ===================
 
-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.
+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.
 
 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.
 
 
=== modified file 'doc/source/management/sql_no_fcache.rst'
--- doc/source/management/sql_no_fcache.rst	2011-10-07 00:55:06 +0000
+++ doc/source/management/sql_no_fcache.rst	2012-12-13 13:30:28 +0000
@@ -18,7 +18,7 @@
 Version-Specific Information
 ============================
 
-  * 5.1.49-12.0:
+  * :rn:`5.1.49-rel12.0`:
     Full functionality available.
 
 Other Information
 
=== modified file 'doc/source/management/udf_maatkit.rst'
--- doc/source/management/udf_maatkit.rst	2011-10-07 00:55:06 +0000
+++ doc/source/management/udf_maatkit.rst	2012-12-13 13:30:28 +0000
@@ -15,7 +15,7 @@
 Version Specific Information
 ============================
 
-  * 5.1.53-12.4:
+  * :rn:`5.1.53-12.4`:
     Began distributing ``fnv_udf``, ``fnv1a_udf``, and ``murmur_udf``.
 
 Other Information
 
=== modified file 'doc/source/performance/handlersocket.rst'
--- doc/source/performance/handlersocket.rst	2011-10-07 00:55:06 +0000
+++ doc/source/performance/handlersocket.rst	2012-12-13 13:30:28 +0000
@@ -19,7 +19,7 @@
 Version Specific Information
 ============================
 
-  * 5.1.52-12.3
+  * :rn:`5.1.52-12.3`
     Full functionality available.
 
 Other Information
 
=== modified file 'doc/source/performance/innodb_doublewrite_path.rst'
--- doc/source/performance/innodb_doublewrite_path.rst	2011-10-07 00:55:06 +0000
+++ doc/source/performance/innodb_doublewrite_path.rst	2012-12-13 13:30:28 +0000
@@ -50,16 +50,16 @@
 
 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.
 
-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.
+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.
 
 
 Version Specific Information
 ============================
 
-  * 5.1.47-11.0	 
+  * :rn:`5.1.47-rel11.1`
     Full functionality available.
 
-  * 5.1.53-12.4
+  * :rn:`5.1.53-12.4`
     Rebuild of database and system files no longer necessary.
 
 System Variables
 
=== modified file 'doc/source/performance/innodb_lazy_drop_table.rst'
--- doc/source/performance/innodb_lazy_drop_table.rst	2012-01-27 11:37:42 +0000
+++ doc/source/performance/innodb_lazy_drop_table.rst	2012-12-13 13:30:28 +0000
@@ -4,14 +4,14 @@
 Drop table performance
 ======================
 
-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.
+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.
 
 This feature allows you to do "background table drop".
 
 Version Specific Information
 ============================
 
-  * 5.1.56-12-7 Feature added.
+  * :rn:`5.1.56-12.7` Feature added.
 
 System Variables
 ================
@@ -26,7 +26,7 @@
    :default: FALSE
    :range: TRUE/FALSE
 
-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.
+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.
 
 When this option is OFF, the usual behavior for dropping tables is in effect.
 
 
=== modified file 'doc/source/performance/innodb_purge_thread.rst'
--- doc/source/performance/innodb_purge_thread.rst	2011-10-07 00:55:06 +0000
+++ doc/source/performance/innodb_purge_thread.rst	2012-12-13 13:30:28 +0000
@@ -61,6 +61,6 @@
 
   * `Tuning for heavy writing workloads <http://www.mysqlperformanceblog.com/2009/10/14/tuning-for-heavy-writing-workloads/>`_
 
-  * `Reasons for run-away main |InnoDB| tablespace <http://www.mysqlperformanceblog.com/2009/10/14/tuning-for-heavy-writing-workloads/>`_
+  * `Reasons for run-away main InnoDB tablespace <http://www.mysqlperformanceblog.com/2010/06/10/reasons-for-run-away-main-innodb-tablespace/>`_
 
-  * `Purge thread spiral of death <http://www.mysqlperformanceblog.com/2009/10/14/tuning-for-heavy-writing-workloads/>`_
+  * `Purge thread spiral of death <http://www.mysqlperformanceblog.com/2010/06/10/purge-thread-spira-of-death/>`_
 
=== modified file 'doc/source/performance/remove_fcntl_excessive_calls.rst'
--- doc/source/performance/remove_fcntl_excessive_calls.rst	2012-10-19 10:36:02 +0000
+++ doc/source/performance/remove_fcntl_excessive_calls.rst	2012-12-13 13:30:28 +0000
@@ -20,7 +20,7 @@
 Version Specific Information
 ============================
 
-  * :rn:`5.1.49-12.0`: 
+  * :rn:`5.1.49-rel12.0`: 
     Feature implemented 
   * :rn:`5.1.55-12.6`: 
     Feature updated
 
=== modified file 'doc/source/release-notes/Percona-Server-5.1.50-rel12.1.rst'
--- doc/source/release-notes/Percona-Server-5.1.50-rel12.1.rst	2012-10-13 08:58:19 +0000
+++ doc/source/release-notes/Percona-Server-5.1.50-rel12.1.rst	2012-12-13 13:30:28 +0000
@@ -17,7 +17,7 @@
 
     * :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*)
 
-    * :ref:`innodb_expand_import_page` - Implemented more exact checking to avoid corruption of the ``.ibd`` file using :variable:`innodb_expand_export`. (*Yasufumi Kinoshita*)
+    * :ref:`innodb_expand_import_page` - Implemented more exact checking to avoid corruption of the ``.ibd`` file using :variable:`innodb_expand_import`. (*Yasufumi Kinoshita*)
 
     * :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*)
 
 
=== renamed file 'doc/source/reliability/innodb_recovery_update_relay_log.rst' => 'doc/source/reliability/crash_resistant_replication.rst'
--- doc/source/reliability/innodb_recovery_update_relay_log.rst	2012-06-13 10:52:23 +0000
+++ doc/source/reliability/crash_resistant_replication.rst	2012-12-13 13:30:28 +0000
@@ -59,7 +59,7 @@
 
 .. variable:: innodb_overwrite_relay_log_info
 
-     :version 5.5.10-20.1: Renamed.
+     :version 1.0.3-4: Introduced
      :cli: Yes
      :conf: Yes
      :scope: Global
 
=== modified file 'doc/source/reliability/error_pad.rst'
--- doc/source/reliability/error_pad.rst	2011-10-07 00:55:06 +0000
+++ doc/source/reliability/error_pad.rst	2012-12-13 13:30:28 +0000
@@ -51,5 +51,5 @@
 Version-Specific Information
 ============================
 
-  * 5.1.49-12.0:
+  * :rn:`5.1.49-rel12.0`
     Full functionality available.
 
=== modified file 'doc/source/reliability/log_connection_error.rst'
--- doc/source/reliability/log_connection_error.rst	2011-10-07 00:55:06 +0000
+++ doc/source/reliability/log_connection_error.rst	2012-12-13 13:30:28 +0000
@@ -10,5 +10,5 @@
 Version-Specific Information
 ============================
 
-  * 5.1.49-12.0:
+  * :rn:`5.1.49-rel12.0`
     Full functionality available.
 
=== modified file 'doc/source/reliability/show_slave_status_nolock.rst'
--- doc/source/reliability/show_slave_status_nolock.rst	2012-09-03 09:31:43 +0000
+++ doc/source/reliability/show_slave_status_nolock.rst	2012-12-13 13:30:28 +0000
@@ -21,5 +21,4 @@
 Version Specific Information
 ============================
 
-  * 5.1.52-12.3:
-    Currently only the source code is distributed; the feature is not included in binaries.
+  * :rn:`5.1.52-12.3` - Introduced
 
=== modified file 'doc/source/scalability/innodb_extra_rseg.rst'
--- doc/source/scalability/innodb_extra_rseg.rst	2012-05-29 17:18:20 +0000
+++ doc/source/scalability/innodb_extra_rseg.rst	2012-12-13 13:30:28 +0000
@@ -10,7 +10,9 @@
 
 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).
 
-**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|.
+.. 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|.
 
 
 System Variables
@@ -40,8 +42,6 @@
 
 The result should be the number of extra segments + 1 (as a default single segment always exists).
 
- 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.
-
 
 ``INFORMATION_SCHEMA`` Tables
 =============================
 
=== modified file 'doc/source/scalability/innodb_io.rst'
--- doc/source/scalability/innodb_io.rst	2012-10-05 10:57:57 +0000
+++ doc/source/scalability/innodb_io.rst	2012-12-13 13:30:28 +0000
@@ -36,7 +36,7 @@
 
 .. variable:: innodb_adaptive_checkpoint
 
-   :version: 5.1.54-12.5 Added 
+   :version 5.1.54-12.5: Added 
    :cli: Yes
    :conf: Yes
    :scope: Global
@@ -109,7 +109,7 @@
 
 .. variable:: innodb_flush_log_at_trx_commit_session
 
-     :version: 5.1.49-13 Added
+     :version 5.1.49-rel11.3: Added
      :cli: Yes
      :conf: Yes
      :scope: Global