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

[Hrvoje Matijakovic]

[Alexey Kopytov (akopytov)]

Unless I'm missing something obvious, the release notes entry was correct, no need to remove it.

review: Needs Fixing

[Alexey Kopytov (akopytov)]

review: Approve

[Laurynas Biveinis (laurynas-biveinis)]

Where is mysqldump --innodb-optimize-keys documented now?

[Hrvoje Matijakovic (hrvojem)]

http://www.percona.com/doc/percona-server/5.5/management/innodb_extended_fast_index_creation.html

[Laurynas Biveinis (laurynas-biveinis)]

Hrvoje - thanks.

=== modified file 'doc/source/management/innodb_fast_index_creation.rst'
--- doc/source/management/innodb_fast_index_creation.rst	2012-02-13 08:49:21 +0000
+++ doc/source/management/innodb_fast_index_creation.rst	2012-07-06 08:06:22 +0000
@@ -4,7 +4,7 @@
  Fast Index Creation
 =====================
 
-Percona has implemented several changes related to |MySQL| 's fast index creation feature. This feature extends the ``ALTER TABLE`` command by adding a new clause that provides online index renaming capability, that is renaming indexes without rebuilding the whole table.
+Percona has implemented several changes related to |MySQL|'s fast index creation feature. Extended features, besides disabling :variable:`fast_index_creation`, can be enabled with :variable:`expand_fast_index_creation`. 
 
 Disabling Fast Index Creation
 =============================
@@ -14,32 +14,6 @@
 This feature implements a session variable that disables fast index creation. This causes indexes to be created in the way they were created before fast index creation was implemented. While this is slower, it avoids the problem of data dictionary inconsistency between |MySQL| and |InnoDB|.
 
 
-:command:`mysqldump`
---------------------
-
-A new option, ``--innodb-optimize-keys``, was implemented in :command:`mysqldump`. It changes the way |InnoDB| tables are dumped, so that secondary and foreign keys are created after loading the data, thus taking advantage of fast index creation. More specifically:
-
-  * ``KEY``, ``UNIQUE KEY``, and ``CONSTRAINT`` clauses are omitted from ``CREATE TABLE`` statements corresponding to |InnoDB| tables.
-
-  * An additional ``ALTER TABLE`` is issued after dumping the data, in order to create the previously omitted keys.
-
-Delaying foreign key creation does not introduce any additional risks, as :command:`mysqldump` always prepends its output with ``SET FOREIGN_KEY_CHECKS=0`` anyway.
-
-
-``ALTER TABLE``
----------------
-
-When ``ALTER TABLE`` requires a table copy, secondary keys are now dropped and recreated later, after copying the data. The following restrictions apply:
-
-  * Only non-unique keys can be involved in this optimization.
-
-  * If the table contains foreign keys, or a foreign key is being added as a part of the current ``ALTER TABLE`` statement, the optimization is disabled for all keys.
-
-``OPTIMIZE TABLE``
-------------------
-
-Internally, ``OPTIMIZE TABLE`` is mapped to ``ALTER TABLE ... ENGINE=innodb`` for |InnoDB| tables. As a consequence, it now also benefits from fast index creation, with the same restrictions as for ``ALTER TABLE``.
-
 
 Version Specific Information
 ============================