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

[Hrvoje Matijakovic]

[Stewart Smith (stewart)]

review: Approve

=== added file 'doc/source/flexibility/innodb_files_extend.rst'
--- doc/source/flexibility/innodb_files_extend.rst	1970-01-01 00:00:00 +0000
+++ doc/source/flexibility/innodb_files_extend.rst	2013-03-21 21:00:31 +0000
@@ -0,0 +1,24 @@
+.. _innodb_files_extend:
+
+================================
+ Support of Multiple Page Sizes
+================================
+
+.. warning:: This feature has been deprecated in the |Percona Server| :rn:`5.5.30-30.2`. It has been replaced by the `upstream <http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_page_size>`_ version released in |MySQL| 5.6.4.
+
+|Percona Server| has implemented support for multiple |InnoDB| page sizes. This can be used to increase the IO performance by setting this value close to storage device block size. |InnoDB| page size can be set up with the :variable:`innodb_page_size` variable.
+
+System Variables
+================
+
+.. variable:: innodb_page_size
+
+     :cli: Yes
+     :conf: Yes
+     :scope: Global
+     :dyn: No
+     :vartype: ULONG
+     :default: 16384
+     :range: 4096, 8192, 16384
+
+**EXPERIMENTAL**: The universal page size of the database. Changing for an existing database is not supported. Use at your own risk!

=== removed file 'doc/source/flexibility/innodb_files_extend.rst'
--- doc/source/flexibility/innodb_files_extend.rst	2013-01-30 10:01:50 +0000
+++ doc/source/flexibility/innodb_files_extend.rst	1970-01-01 00:00:00 +0000
@@ -1,25 +0,0 @@
-.. _innodb_files_extend:
-
-================================
- Support of Multiple Page Sizes
-================================
-
-In standard |InnoDB|, the size of the read-ahead area is computed dynamically, but it always has the same value. This change makes the size fixed, avoiding unuseful computations.
-
-This feature adds a new system variable for setting it.
-
-
-System Variables
-================
-
-.. variable:: innodb_page_size
-
-     :cli: Yes
-     :conf: Yes
-     :scope:
-     :dyn: No
-     :vartype: ULONG
-     :default: 1 « 14
-     :range: 1 « 12 to 1 « ``UNIV_PAGE_SIZE_SHIFT_MAX``
-
-**EXPERIMENTAL**: The universal page size of the database. Changing for an existing database is not supported. Use at your own risk!

=== modified file 'doc/source/index.rst'
--- doc/source/index.rst	2013-03-08 12:42:38 +0000
+++ doc/source/index.rst	2013-03-21 21:00:31 +0000
@@ -123,7 +123,7 @@
    management/innodb_fast_index_creation
    management/innodb_expanded_fast_index_creation
    management/sql_no_fcache
-   management/udf_maatkit
+   management/udf_percona_toolkit
    management/innodb_fake_changes
    management/innodb_kill_idle_trx
    management/enforce_engine
@@ -160,7 +160,6 @@
    :glob:
 
    management/innodb_buffer_pool_shm
-   performance/innodb_purge_thread
 
 Reference
 =========

=== modified file 'doc/source/installation.rst'
--- doc/source/installation.rst	2013-02-06 10:26:45 +0000
+++ doc/source/installation.rst	2013-03-21 21:00:31 +0000
@@ -25,7 +25,7 @@
    installation/apt_repo
    installation/yum_repo
 
-|Percona| provides repositories for :program:`yum` (``RPM`` packages for *Red Hat*, *CentOS* and *Amazon Linux AMI*) and :program:`apt` (:file:`.deb` packages for *Ubuntu* and *Debian*) for software such as |Percona Server|, |XtraDB|, |XtraBackup|, and *Maatkit*. This makes it easy to install and update your software and its dependencies through your operating system's package manager.
+|Percona| provides repositories for :program:`yum` (``RPM`` packages for *Red Hat*, *CentOS* and *Amazon Linux AMI*) and :program:`apt` (:file:`.deb` packages for *Ubuntu* and *Debian*) for software such as |Percona Server|, |XtraDB|, |XtraBackup|, and *Percona Toolkit*. This makes it easy to install and update your software and its dependencies through your operating system's package manager.
 
 This is the recommend way of installing where possible.
 

=== modified file 'doc/source/management/innodb_lru_dump_restore.rst'
--- doc/source/management/innodb_lru_dump_restore.rst	2012-12-14 09:58:23 +0000
+++ doc/source/management/innodb_lru_dump_restore.rst	2013-03-21 21:00:31 +0000
@@ -22,7 +22,7 @@
 Manual Operation
 ================
 
-Manual dump/restore is done through the ``INFORMATION_SCHEMA`` using the following two administrative commands (see ``XTRADB_ADMIN_COMMAND``):
+Manual dump/restore is done through the ``INFORMATION_SCHEMA`` using the following two administrative commands:
 
   * ``XTRA_LRU_DUMP``: 
     Dumps the contents of the buffer pool (a list of space_id and page_no) to the file ib_lru_dump in the directory specified by the datadir configuration setting.

=== removed file 'doc/source/management/udf_maatkit.rst'
--- doc/source/management/udf_maatkit.rst	2012-12-14 09:58:23 +0000
+++ doc/source/management/udf_maatkit.rst	1970-01-01 00:00:00 +0000
@@ -1,48 +0,0 @@
-.. _udf_maatkit:
-
-======================================
- *Percona Toolkit* and *Maatkit* UDFs
-======================================
-
-Three *Percona Toolkit* and *Maatkit* UDFs that provide faster checksums are provided:
-
-  * ``libfnv_udf``
-
-  * ``libfnv1a_udf``
-
-  * ``libmurmur_udf``
-
-Tools that do checksumming of data (pt-table-checksum, pt-table-sync) will use these functions if they are installed. These are much faster and have better data distribution than CRC32() or MD5() or similar, which are the default functions built into |MySQL|.
-
-Version Specific Information
-============================
-
-  * :rn:`5.5.8-20.0`:
-    Began distributing ``libfnv_udf``, ``libfnv1a_udf``, and ``libmurmur_udf``.
-
-Other Information
-=================
-
-  * Author / Origin:
-    Baron Schwartz
-
-Installation
-============
-
-These functions are  distributed with the |Percona Server| installation. Installing the |Percona Server| will place the UDFs onto your system. However, they will not yet be installed into the |MySQL| server. To install one of the UDF's into the server, execute one of the following commands, depending on which UDF you want to install: ::
-
-  $ mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME 'libfnv_udf.so'" 
-  $ mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME 'libfnv1a_udf.so'" 
-  $ mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME 'libmurmur_udf.so'"
-
-Executing each of these commands will install its respective UDF into the server.
-
-Confirm that the installation succeeded by running a command such as :: 
-
-  mysql> SELECT fnv_64('hello world');
-
-Other Reading
-=============
-
-  * *Percona Toolkit* - http://www.percona.com/doc/percona-toolkit
-  * *Maatkit* - http://www.maatkit.org/

=== added file 'doc/source/management/udf_percona_toolkit.rst'
--- doc/source/management/udf_percona_toolkit.rst	1970-01-01 00:00:00 +0000
+++ doc/source/management/udf_percona_toolkit.rst	2013-03-21 21:00:31 +0000
@@ -0,0 +1,54 @@
+.. _udf_percona_toolkit:
+
+========================
+ *Percona Toolkit* UDFs
+========================
+
+Three *Percona Toolkit* UDFs that provide faster checksums are provided:
+
+  * ``fnv_udf``
+
+  * ``fnv1a_udf``
+
+  * ``murmur_udf``
+
+Version Specific Information
+============================
+
+  * :rn:`5.5.8-20.0`:
+    Began distributing ``fnv_udf``, ``fnv1a_udf``, and ``murmur_udf``.
+
+Other Information
+=================
+
+  * Author / Origin:
+    Baron Schwartz
+
+Installation
+============
+
+Use of the Percona Software Repositories simplifies the installation of *Percona Toolkit*. Once the repository has been set up on your system, *Percona Toolkit* can be installed by executing: ::
+
+  $ yum install percona-toolkit
+
+This will place the *Percona Toolkit* UDFs onto your system. However, they will not yet be installed into the |MySQL| server. To install one of the UDF``s into the server, execute one of the following commands, depending on which UDF you want to install: ::
+
+  $ mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME ``fnv_udf.so``" 
+  $ mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME ``fnv1a_udf.so``" 
+  $ mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME ``murmur_udf.so``"
+
+Executing each of these commands will install its respective UDF into the server.
+
+Troubleshooting
+================
+
+If you get the error: :: 
+
+  ERROR 1126 (HY000): Can't open shared library 'fnv_udf.so' (errno: 22 fnv_udf.so: cannot open shared object file: No such file or directory)
+
+Then you may need to copy the .so file to another location in your system. Try both ``/lib`` and ``/usr/lib``. Look at your environment's ``$LD_LIBRARY_PATH`` variable for clues. If none is set, and neither ``/lib`` nor ``/usr/lib`` works, you may need to set ``LD_LIBRARY_PATH`` to ``/lib`` or ``/usr/lib``.
+
+Other Reading
+=============
+
+  * *Percona Toolkit* `documentation <http://www.percona.com/doc/percona-toolkit/>`_

=== removed file 'doc/source/percona-theme/static/boxes_header_bulletpoint.png.moved'
Binary files doc/source/percona-theme/static/boxes_header_bulletpoint.png.moved	2012-07-12 08:48:23 +0000 and doc/source/percona-theme/static/boxes_header_bulletpoint.png.moved	1970-01-01 00:00:00 +0000 differ
=== removed file 'doc/source/percona-theme/static/button-download-icon.png.moved'
Binary files doc/source/percona-theme/static/button-download-icon.png.moved	2012-07-12 08:48:23 +0000 and doc/source/percona-theme/static/button-download-icon.png.moved	1970-01-01 00:00:00 +0000 differ
=== removed file 'doc/source/percona-theme/static/content_list_bulletpoint.png.moved'
Binary files doc/source/percona-theme/static/content_list_bulletpoint.png.moved	2012-07-12 08:48:23 +0000 and doc/source/percona-theme/static/content_list_bulletpoint.png.moved	1970-01-01 00:00:00 +0000 differ
=== removed file 'doc/source/percona-theme/static/side_buttons.png.moved'
Binary files doc/source/percona-theme/static/side_buttons.png.moved	2012-07-12 08:48:23 +0000 and doc/source/percona-theme/static/side_buttons.png.moved	1970-01-01 00:00:00 +0000 differ
=== removed file 'doc/source/performance/innodb_purge_thread.rst'
--- doc/source/performance/innodb_purge_thread.rst	2012-09-27 09:13:48 +0000
+++ doc/source/performance/innodb_purge_thread.rst	1970-01-01 00:00:00 +0000
@@ -1,7 +0,0 @@
-.. _innodb_purge_thread:
-
-========================
- Dedicated Purge Thread
-========================
-
-  The |Percona Server| 5.1 multiple purge threads feature has not been ported to 5.5 yet. However, the upstream MySQL 5.5 dedicated purge thread is available.

=== added file 'doc/source/performance/query_cache_enhance.rst'
--- doc/source/performance/query_cache_enhance.rst	1970-01-01 00:00:00 +0000
+++ doc/source/performance/query_cache_enhance.rst	2013-03-21 21:00:31 +0000
@@ -0,0 +1,89 @@
+.. _query_cache_enhance:
+
+==========================
+ Query Cache Enhancements
+==========================
+
+This page describes the enhancements for the query cache. At the moment three features are available:
+
+  * Disabling the cache completely
+
+  * Diagnosing contention more easily
+
+  * Ignoring comments
+
+Disabling the cache completely
+==============================
+
+This feature allows the user to completely disable use of the query cache. When the server is compiled with the query cache enabled, the query cache is locked during use by the query cache mutex. This lock can cause performance to decrease in some situations. By disabling use of the query cache altogether when the server is started, any possibility of locking it is eliminated, and performance may be improved.
+
+The query cache can now be disabled at server startup or in an option file by: ::
+
+  --query_cache_type=0
+
+The default is 1 (query cache enabled).
+
+**Note:** This variable already exists in standard |MySQL|, but when setting query_cache_type=0, the query cache mutex will still be in used. Setting query_cache_type=0 in |Percona Server| ensures that both the cache is disabled and the mutex is not used.
+
+If query caching is off and a user tries to turn it on from within a session, the following error will be reported: ::
+
+  SET GLOBAL query_cache_type=ON;
+  ERROR 1651(HY000): Query cache is disabled; restart the server with query_cache_type=1 to enable it
+
+**Note:** This variable is implemented in standard |MySQL| from version 5.5.0.
+
+
+Diagnosing contention more easily
+=================================
+
+This features provides a new thread state - ``Waiting on query cache mutex``. It has always been difficult to spot query cache bottlenecks because these bottlenecks usually happen intermittently and are not directly reported by the server. This new thread state appear in the output of SHOW PROCESSLIST, easing diagnostics.
+
+Imagine that we run three queries simultaneously (each one in a separate thread):
+
+  > SELECT number from t where id > 0;
+  > SELECT number from t where id > 0;
+  > SELECT number from t where id > 0;
+
+If we experience query cache contention, the output of SHOW PROCESSLIT will look like this: ::
+
+  > SHOW PROCESSLIST;
+  Id      User    Host            db      Command Time    State                          Info
+  2       root    localhost       test    Sleep   2       NULL
+  3       root    localhost       test    Query   2       Waiting on query cache mutex  SELECT number from t where id > 0;
+  4       root    localhost       test    Query   1       Waiting on query cache mutex   SELECT number from t where id > 0;
+  5       root    localhost       test    Query   0       NULL
+
+Ignoring comments
+=================
+
+This feature adds an option to make the server ignore comments when checking for a query cache hit. For example, consider these two queries: ::
+
+  /* first query  */ select name from users where users.name like 'Bob%';
+  /* retry search */ select name from users where users.name like 'Bob%';
+
+By default (option off), the queries are considered different, so the server will execute them both and cache them both.
+
+If the option is enabled, the queries are considered identical, so the server will execute and cache the first one and will serve the second one directly from the query cache.
+
+
+System Variables
+================
+
+.. variable:: query_cache_strip_comments
+
+   :cli: Yes
+   :conf: Yes
+   :scope: Global
+   :dyn: Yes
+   :vartype: Boolean
+   :default: Off
+
+
+Makes the server ignore comments when checking for a query cache hit.
+
+Other Reading
+-------------
+
+  * `MySQL general thread states <http://dev.mysql.com/doc/refman/5.1/en/general-thread-states.html>`_
+
+  * `Query cache freezes <http://www.mysqlperformanceblog.com/2009/03/19/mysql-random-freezes-could-be-the-query-cache/>`_

=== removed file 'doc/source/performance/query_cache_enhance.rst'
--- doc/source/performance/query_cache_enhance.rst	2012-09-27 09:13:48 +0000
+++ doc/source/performance/query_cache_enhance.rst	1970-01-01 00:00:00 +0000
@@ -1,123 +0,0 @@
-.. _query_cache_enhance:
-
-==========================
- Query Cache Enhancements
-==========================
-
-This page describes the enhancements for the query cache. At the moment three features are available:
-
-  * Disabling the cache completely
-
-  * Diagnosing contention more easily
-
-  * Ignoring comments
-
-Disabling the cache completely
-==============================
-
-This feature allows the user to completely disable use of the query cache. When the server is compiled with the query cache enabled, the query cache is locked during use by the query cache mutex. This lock can cause performance to decrease in some situations. By disabling use of the query cache altogether when the server is started, any possibility of locking it is eliminated, and performance may be improved.
-
-The query cache can now be disabled at server startup or in an option file by: ::
-
-  --query_cache_type=0
-
-The default is 1 (query cache enabled).
-
-**Note:** This variable already exists in standard |MySQL|, but when setting query_cache_type=0, the query cache mutex will still be in used. Setting query_cache_type=0 in |Percona Server| ensures that both the cache is disabled and the mutex is not used.
-
-If query caching is off and a user tries to turn it on from within a session, the following error will be reported: ::
-
-  SET GLOBAL query_cache_type=ON;
-  ERROR 1651(HY000): Query cache is disabled; restart the server with query_cache_type=1 to enable it
-
-**Note:** This variable is implemented in standard |MySQL| from version 5.5.0.
-
-
-Diagnosing contention more easily
-=================================
-
-This features provides a new thread state - ``Waiting on query cache mutex``. It has always been difficult to spot query cache bottlenecks because these bottlenecks usually happen intermittently and are not directly reported by the server. This new thread state appear in the output of SHOW PROCESSLIST, easing diagnostics.
-
-Imagine that we run three queries simultaneously (each one in a separate thread):
-
-  > SELECT number from t where id > 0;
-  > SELECT number from t where id > 0;
-  > SELECT number from t where id > 0;
-
-If we experience query cache contention, the output of SHOW PROCESSLIT will look like this: ::
-
-  > SHOW PROCESSLIST;
-  Id      User    Host            db      Command Time    State                          Info
-  2       root    localhost       test    Sleep   2       NULL
-  3       root    localhost       test    Query   2       Waiting on query cache mutex  SELECT number from t where id > 0;
-  4       root    localhost       test    Query   1       Waiting on query cache mutex   SELECT number from t where id > 0;
-  5       root    localhost       test    Query   0       NULL
-
-Ignoring comments
-=================
-
-This feature adds an option to make the server ignore comments when checking for a query cache hit. For example, consider these two queries: ::
-
-  /* first query  */ select name from users where users.name like 'Bob%';
-  /* retry search */ select name from users where users.name like 'Bob%';
-
-By default (option off), the queries are considered different, so the server will execute them both and cache them both.
-
-If the option is enabled, the queries are considered identical, so the server will execute and cache the first one and will serve the second one directly from the query cache.
-
-
-.. Version Specific Information
-.. ----------------------------
-
-.. Disabling the query cache completely
-
-..  Percona Server Version	 Comments
-.. 5.1.49-12.0	 Full functionality available.
-.. Diagnosing contention more easily
-
-..  Percona Server Version	 Comments
-.. 5.1.49-12.0	 Full functionality available.
-.. Ignoring comments
-
-..  Percona Server Version	 Comments
-.. 5.1.47-11.0	 Critical bug (see MySQL bug 55032). Release was recalled.
-.. 5.1.47-11.1	 Fixed critical bug from previous release. MySQL bug 55032 actual. Bug b603618 actual. Bug 603619 actual.
-.. 5.1.47-11.2	 Full functionality available.
-.. 5.1.48-12.0	 Full functionality available.
-
-.. Other Information
-
-.. Disabling the query cache completely
-
-.. Author/Origin	 Percona
-.. Bugs fixed	LP bug 609027, MySQL bug 38551
-.. Diagnosing contention more easily
-
-.. Author/Origin	 Percona
-.. Bugs fixed	LP bug589484
-
-System Variables
-================
-
-.. variable:: query_cache_strip_comments
-
-   :cli: Yes
-   :conf: Yes
-   :scope: Global
-   :dyn: Yes
-   :vartype: Boolean
-   :default: Off
-
-
-Makes the server ignore comments when checking for a query cache hit.
-
-Other Reading
--------------
-
-  * `MySQL general thread states <http://dev.mysql.com/doc/refman/5.1/en/general-thread-states.html>`_
-
-  * `RAII <http://en.wikibooks.org/wiki/More_C%2B%2B_Idioms/Resource_Acquisition_Is_Initialization>`_
-
-  * `Scope guard <http://en.wikibooks.org/wiki/More_C%2B%2B_Idioms/Scope_Guard>`_
-
-  * `Query cache freezes <http://www.mysqlperformanceblog.com/2009/03/19/mysql-random-freezes-could-be-the-query-cache/>`_

=== modified file 'doc/source/release-notes/Percona-Server-5.5.15-21.0.rst'
--- doc/source/release-notes/Percona-Server-5.5.15-21.0.rst	2012-10-24 18:06:58 +0000
+++ doc/source/release-notes/Percona-Server-5.5.15-21.0.rst	2013-03-21 21:00:31 +0000
@@ -4,7 +4,7 @@
 |Percona Server| 5.5.15-21.0
 ============================
 
-Percona is glad to announce the release of |Percona Server| 5.5.15-21.0 on August 31, 2011 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.5/Percona-Server-5.5.15-21.0/>`_ and from the `Percona Software Repositories <http://http://www.percona.com/doc/percona-server/5.5/installation.html>`_).
+Percona is glad to announce the release of |Percona Server| 5.5.15-21.0 on August 31, 2011 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.5/Percona-Server-5.5.15-21.0/>`_ and from the `Percona Software Repositories <http://www.percona.com/doc/percona-server/5.5/installation.html>`_).
 
 Based on |MySQL| 5.5.15, including all the bug fixes in it, |Percona Server| 5.5.15-21.0 is now the current stable release in the 5.5 series. All of Percona's software is open-source and free, all the details of the release can be found in the `5.5.15-21.0 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.5.15-21.0>`_.
 

=== modified file 'doc/source/release-notes/Percona-Server-5.5.28-29.3.rst'
--- doc/source/release-notes/Percona-Server-5.5.28-29.3.rst	2013-01-09 07:42:33 +0000
+++ doc/source/release-notes/Percona-Server-5.5.28-29.3.rst	2013-03-21 21:00:31 +0000
@@ -4,7 +4,7 @@
  |Percona Server| 5.5.28-29.3
 ===============================
 
-Percona is glad to announce the release of |Percona Server| 5.5.28-29.3 on January 8th, 2012 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.5/Percona-Server-5.5.28-29.3/>`_ and from the `Percona Software Repositories <http://www.percona.com/docs/wiki/repositories:start>`_).
+Percona is glad to announce the release of |Percona Server| 5.5.28-29.3 on January 8th, 2013 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.5/Percona-Server-5.5.28-29.3/>`_ and from the `Percona Software Repositories <http://www.percona.com/docs/wiki/repositories:start>`_).
 
 Based on `MySQL 5.5.28 <http://dev.mysql.com/doc/refman/5.5/en/news-5.5.28.html>`_, including all the bug fixes in it, |Percona Server| 5.5.28-29.3 is now the current stable release in the 5.5 series. All of |Percona|'s software is open-source and free, all the details of the release can be found in the `5.5.28-29.3 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.5.28-29.3>`_. 
 

=== modified file 'doc/source/release-notes/Percona-Server-5.5.29-29.4.rst'
--- doc/source/release-notes/Percona-Server-5.5.29-29.4.rst	2013-01-30 10:01:50 +0000
+++ doc/source/release-notes/Percona-Server-5.5.29-29.4.rst	2013-03-21 21:00:31 +0000
@@ -4,7 +4,7 @@
  |Percona Server| 5.5.29-29.4
 ===============================
 
-Percona is glad to announce the release of |Percona Server| 5.5.29-29.4 on January 23rd, 2012 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.5/Percona-Server-5.5.29-29.4/>`_ and from the `Percona Software Repositories <http://www.percona.com/docs/wiki/repositories:start>`_).
+Percona is glad to announce the release of |Percona Server| 5.5.29-29.4 on January 23rd, 2013 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.5/Percona-Server-5.5.29-29.4/>`_ and from the `Percona Software Repositories <http://www.percona.com/docs/wiki/repositories:start>`_).
 
 Based on `MySQL 5.5.29 <http://dev.mysql.com/doc/refman/5.5/en/news-5.5.29.html>`_, including all the bug fixes in it, |Percona Server| 5.5.29-29.4 is now the current stable release in the 5.5 series. All of |Percona|'s software is open-source and free, all the details of the release can be found in the `5.5.29-29.4 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.5.29-29.4>`_.