Merge lp:~hrvojem/percona-server/rn-5.5.27-28.0 into lp:percona-server/5.5

[Hrvoje Matijakovic]

[Laurynas Biveinis (laurynas-biveinis)]

   "...greater than value, the value of option_name will simply be set
   to value." Too many "values". Likewise for minimum. Rename the
   minumum/maximum "value" to something else.

   Please "show warnings" output to the minimum value violation
   example too.

   Bug https://bugs.launchpad.net/bugs/592377 is missing from the RN.
   It should be added to the new features section.

   For bugs 1026926 and 1015109 please say which version the
   regression was introduced in.

   For bug 1035225, please mention that this is MySQL and not Percona
   Server specific bug, add the upstream bug link.

   For bug 890623, more user-friendly description would be "Removed
   error log warnings that occured after enabling
   innodb_use_sys_stats_table and before ANALYZE TABLE is run for each
   table" or similar.

   For bug 1013432, "Fixed the malformed CHANGE MASTER query in the
   output of mysqldump..."

review: Needs Fixing

[Laurynas Biveinis (laurynas-biveinis)]

review: Approve

=== modified file 'doc/source/conf.py'
--- doc/source/conf.py	2012-07-18 08:43:52 +0000
+++ doc/source/conf.py	2012-08-22 15:04:31 +0000
@@ -54,7 +54,7 @@
 # The short X.Y version.
 version = '5.5'
 # The full version, including alpha/beta/rc tags.
-release = '5.5.25a-27.1'
+release = '5.5.27-28.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

=== modified file 'doc/source/diagnostics/index_info_schema_tables.rst'
--- doc/source/diagnostics/index_info_schema_tables.rst	2011-10-07 23:38:41 +0000
+++ doc/source/diagnostics/index_info_schema_tables.rst	2012-08-22 15:04:31 +0000
@@ -34,4 +34,5 @@
 
   * :table:`TEMPORARY_TABLES`
 
+  * :table:`INNODB_UNDO_LOGS`
 

=== modified file 'doc/source/diagnostics/misc_info_schema_tables.rst'
--- doc/source/diagnostics/misc_info_schema_tables.rst	2012-03-12 08:04:08 +0000
+++ doc/source/diagnostics/misc_info_schema_tables.rst	2012-08-22 15:04:31 +0000
@@ -133,3 +133,19 @@
    :column UPDATE_TIME: Date and time of the latest update of the temporary table
 
 This table holds information on the temporary tables existing for the running connection.
+
+InnoDB Undo Logs
+================
+
+This table holds the undo segment information. 
+
+.. table:: INFORMATION_SCHEMA.INNODB_UNDO_LOGS
+
+   :column trx_id: Transaction ID
+   :column rseg_id: Rollback segment ID
+   :column useg_id: Undo segment ID
+   :column type: Segment type
+   :column state: Segment state
+   :column size: Segment size
+   
+Each row represents an individual undo segment and contains information about which rollback segment the undo segment is currently owned by, which transaction is currently using the undo segment, and other size and type information for the undo segment. This information is 'live' and calculated for each query of the table.

=== modified file 'doc/source/diagnostics/user_stats.rst'
--- doc/source/diagnostics/user_stats.rst	2012-05-21 16:25:24 +0000
+++ doc/source/diagnostics/user_stats.rst	2012-08-22 15:04:31 +0000
@@ -15,7 +15,7 @@
   * :rn:`5.5.10-20.1`:
      Renamed variable :variable:`userstat_running` to :variable:`userstat`.
   * :rn:`5.5.24-26.0`:
-     TOTAL_CONNECTIONS_SSL column has been added to CLIENT_STATISTICS, THREAD_STATISTICS and USER_STATISTICS tables 
+     TOTAL_SSL_CONNECTIONS column has been added to CLIENT_STATISTICS, THREAD_STATISTICS and USER_STATISTICS tables 
 
 Other Information
 =================
@@ -66,7 +66,7 @@
   :column LOST_CONNECTIONS: The number of this client's connections that were terminated uncleanly.
   :column ACCESS_DENIED: The number of times this client's connections issued commands that were denied.
   :column EMPTY_QUERIES: The number of times this client's connections sent empty queries to the server.
-  :column TOTAL_CONNECTIONS_SSL: The number of times this client's connections connected using SSL to the server.
+  :column TOTAL_SSL_CONNECTIONS: The number of times this client's connections connected using SSL to the server.
 
 
 This table holds statistics about client connections. The Percona version of the feature restricts this table's visibility to users who have the ``SUPER`` or ``PROCESS`` privilege.
@@ -96,7 +96,7 @@
         LOST_CONNECTIONS: 0
            ACCESS_DENIED: 0
            EMPTY_QUERIES: 0
-   TOTAL_CONNECTIONS_SSL: 0
+   TOTAL_SSL_CONNECTIONS: 0
 
 
 .. table:: INFORMATION_SCHEMA.INDEX_STATISTICS
@@ -166,7 +166,7 @@
   :column LOST_CONNECTIONS: int(21)
   :column ACCESS_DENIED: int(21)
   :column EMPTY_QUERIES: int(21)
-  :column TOTAL_CONNECTIONS_SSL: int(21)
+  :column TOTAL_SSL_CONNECTIONS: int(21)
 
 .. table:: INFORMATION_SCHEMA.USER_STATISTICS
 
@@ -191,7 +191,7 @@
   :column LOST_CONNECTIONS: The number of this user's connections that were terminated uncleanly.
   :column ACCESS_DENIED: The number of times this user's connections issued commands that were denied.
   :column EMPTY_QUERIES: The number of times this user's connections sent empty queries to the server.
-  :column TOTAL_CONNECTIONS_SSL: The number of times this user's connections connected using SSL to the server.
+  :column TOTAL_SSL_CONNECTIONS: The number of times this user's connections connected using SSL to the server.
 
 This table contains information about user activity. The |Percona| version of the patch restricts this table's visibility to users who have the ``SUPER`` or ``PROCESS`` privilege.
 
@@ -222,7 +222,7 @@
         LOST_CONNECTIONS: 0
            ACCESS_DENIED: 0
            EMPTY_QUERIES: 0
-   TOTAL_CONNECTIONS_SSL: 0
+   TOTAL_SSL_CONNECTIONS: 0
 
 
 Commands Provided

=== modified file 'doc/source/index.rst'
--- doc/source/index.rst	2012-07-24 12:10:45 +0000
+++ doc/source/index.rst	2012-08-22 15:04:31 +0000
@@ -116,13 +116,15 @@
    management/innodb_expand_import
    management/innodb_lru_dump_restore
    management/innodb_fast_index_creation
-   management/innodb_extended_fast_index_creation
+   management/innodb_expanded_fast_index_creation
    management/sql_no_fcache
    management/udf_maatkit
    management/innodb_fake_changes
    management/innodb_kill_idle_trx
    management/enforce_engine
+   management/utility_user
    management/secure_file_priv_extended
+   management/expanded_program_option_modifiers
 
 Diagnostics Improvements
 ========================

=== added file 'doc/source/management/expanded_program_option_modifiers.rst'
--- doc/source/management/expanded_program_option_modifiers.rst	1970-01-01 00:00:00 +0000
+++ doc/source/management/expanded_program_option_modifiers.rst	2012-08-22 15:04:31 +0000
@@ -0,0 +1,128 @@
+.. _expanded_option_modifiers:
+
+=================================
+Expanded Program Option Modifiers
+=================================
+
+|MySQL| has the concept of `options modifiers <http://dev.mysql.com/doc/refman/5.5/en/option-modifiers.html>`_ which is a simple way to modify either the way that |MySQL| interprets an option or the way the option behaves. Option modifiers are used by simply prepending the name of the modifier and a dash "-" before the actual configuration option name. For example specifying --maximum-query_cache_size=4M on the mysqld commad line or specifying maximum-query_cache_size=4M in the :file:`my.cnf` will prevent any client from setting the :variable:`query_cache_size` value larger than 4MB.
+
+Currently MySQL supports five existing option modifiers:
+  * disable: disables or ignores option_name.
+  * enable: enables option_name.
+  * loose: mysqld will not exit with an error if it does not recognize option_name, but instead it will issue only a warning.
+  * maximum: indicates that a client can not set the value of option_name greater than the limit specified. If the client does attempt to set the value of option_name greater than the limit, the option_name will simply be set to the defined limit.
+  * skip: skips or ignores option_name.
+
+In order to offer more control over option visibility, access and range limits, the following new option modifiers have been added by |Percona Server|:
+  * minimum [minimum-<option_name>=<value>] indicates that clients can not set the value of option_name to less than the limit specified. If the client does attempt to set the value of option_name lesser than the limit, the option_name will simply be set to the defined limit.
+  * hidden [hidden-<option_name>=<TRUE/FALSE>] indicates that clients can not see or modify the value of option_name.
+  * readonly [readonly-<option_name>=<TRUE/FALSE>] indicates that clients can see the value of option_name but can not modify the value.
+
+
+Version Specific Information
+============================
+
+  * :rn:`5.5.27-28.0`
+    Expanded program option modifiers implemented
+
+Examples
+========
+
+Adding the following option to the :file:`my.cnf` will set the minimum limit on :variable:`query_cache_size` ::
+
+  minimum-query_cache_size = 4M
+
+Trying to set up bigger value will work correctly, but if we try to set it up with smaller than the limit, defined minimum limit will be used and warning (1292) will be issued:
+
+Initial :variable:`query_cache_size` size:
+
+.. code-block:: mysql
+
+ mysql> show variables like 'query_cache_size';
+ +------------------+---------+
+ | Variable_name    | Value   |
+ +------------------+---------+
+ | query_cache_size | 8388608 |
+ +------------------+---------+
+ 1 row in set (0.00 sec)
+
+Setting up bigger value:
+
+.. code-block:: mysql
+
+ mysql> set global query_cache_size=16777216;
+ Query OK, 0 rows affected (0.00 sec)
+
+ mysql> show variables like 'query_cache_size';
+ +------------------+----------+
+ | Variable_name    | Value    |
+ +------------------+----------+
+ | query_cache_size | 16777216 |
+ +------------------+----------+
+ 1 row in set (0.00 sec)
+
+Setting up smaller value:
+
+.. code-block:: mysql
+
+ mysql> set global query_cache_size=1048576;
+ Query OK, 0 rows affected, 1 warning (0.00 sec)
+
+ mysql> show warnings;
+ +---------+------+-------------------------------------------------------+
+ | Level   | Code | Message                                               |
+ +---------+------+-------------------------------------------------------+
+ | Warning | 1292 | Truncated incorrect query_cache_size value: '1048576' |
+ +---------+------+-------------------------------------------------------+
+ 1 row in set (0.00 sec)
+
+ mysql> show variables like 'query_cache_size';
+ +------------------+---------+
+ | Variable_name    | Value   |
+ +------------------+---------+
+ | query_cache_size | 4194304 |
+ +------------------+---------+
+ 1 row in set (0.00 sec)
+
+
+Adding following option to :file:`my.cnf` will make :variable:`query_cache_size` hidden. ::  
+
+ hidden-query_cache_size=1
+
+.. code-block:: mysql
+
+ mysql> show variables like 'query_cache%';
+ +------------------------------+---------+
+ | Variable_name                | Value   |
+ +------------------------------+---------+
+ | query_cache_limit            | 1048576 |
+ | query_cache_min_res_unit     | 4096    |
+ | query_cache_strip_comments   | OFF     |
+ | query_cache_type             | ON      |
+ | query_cache_wlock_invalidate | OFF     |
+ +------------------------------+---------+
+ 5 rows in set (0.00 sec)
+
+Adding following option to :file:`my.cnf` will make :variable:`query_cache_size` read-only :: 
+
+ readonly-query_cache_size=1
+
+Trying to change the variable value will result in error: 
+
+.. code-block:: mysql
+
+ mysql> show variables like 'query_cache%';
+ +------------------------------+---------+
+ | Variable_name                | Value   |
+ +------------------------------+---------+
+ | query_cache_limit            | 1048576 |
+ | query_cache_min_res_unit     | 4096    |
+ | query_cache_size             | 8388608 |
+ | query_cache_strip_comments   | OFF     |
+ | query_cache_type             | ON      |
+ | query_cache_wlock_invalidate | OFF     |
+ +------------------------------+---------+
+ 6 rows in set (0.00 sec)
+
+ mysql> set global query_cache_size=16777216;
+ ERROR 1238 (HY000): Variable 'query_cache_size' is a read only variable

=== renamed file 'doc/source/management/innodb_extended_fast_index_creation.rst' => 'doc/source/management/innodb_expanded_fast_index_creation.rst'
--- doc/source/management/innodb_extended_fast_index_creation.rst	2012-01-30 16:36:39 +0000
+++ doc/source/management/innodb_expanded_fast_index_creation.rst	2012-08-22 15:04:31 +0000
@@ -1,12 +1,12 @@
-.. _extended_innodb_fast_index_creation:
-
-============================
-Extended 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.
-
-Enabling Extended Fast Index Creation
+.. _expanded_innodb_fast_index_creation:
+
+============================
+Expanded Fast Index Creation
+============================
+
+Percona has implemented several changes related to |MySQL|'s fast index creation feature. This feature expands the ``ALTER TABLE`` command by adding a new clause that provides online index renaming capability, that is renaming indexes without rebuilding the whole table.
+
+Enabling Expanded Fast Index Creation
 =====================================
 
 Fast index creation was implemented in |MySQL| as a way to speed up the process of adding or dropping indexes on tables with many rows. However, cases have been found in which fast index creation creates an inconsistency between |MySQL| and |InnoDB| data dictionaries.

=== modified file 'doc/source/management/innodb_fast_index_creation.rst'
--- doc/source/management/innodb_fast_index_creation.rst	2012-07-06 08:04:01 +0000
+++ doc/source/management/innodb_fast_index_creation.rst	2012-08-22 15:04:31 +0000
@@ -14,6 +14,11 @@
 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|.
 
 
+Tunable buffer size for fast index creation
+===========================================
+
+|Percona Server| supports tunable buffer size for fast index creation in |InnoDB|. This value was calculated based on the merge block size (which was hardcoded to 1 MB) and the minimum index record size. By adding the session variable :variable:`innodb_merge_sort_block_size` block size that is used in the merge sort can now be adjusted for better performance.
+
 
 Version Specific Information
 ============================
@@ -24,6 +29,8 @@
   * 5.5.11-21.2:
     Expanded the applicability of fast index creation to :command:`mysqldump`, ``ALTER TABLE``, and ``OPTIMIZE TABLE``.
 
+  * 5.5.27-28.0
+    Variable :variable:`innodb_merge_sort_block_size` implemented.
 
 System Variables
 ================
@@ -38,8 +45,19 @@
      :default: ON
      :range: ON/OFF
 
+.. variable:: innodb_merge_sort_block_size
+ 
+     :cli: Yes
+     :conf: Yes
+     :scope: Global
+     :dyn: Yes
+     :vartype: ULONG
+     :default: 1048576 (1M)
+     :range: 1048576 - 1073741824 (1G)
 
 Other Reading
 =============
 
   * `Thinking about running OPTIMIZE on your InnoDB Table? Stop! <http://www.mysqlperformanceblog.com/2010/12/09/thinking-about-running-optimize-on-your-innodb-table-stop/>`_
+
+  * `Building Indexes by Sorting In Innodb <http://www.mysqlperformanceblog.com/2012/06/19/building-indexes-by-sorting-in-innodb-aka-fast-index-creation/>`_

=== added file 'doc/source/management/utility_user.rst'
--- doc/source/management/utility_user.rst	1970-01-01 00:00:00 +0000
+++ doc/source/management/utility_user.rst	2012-08-22 15:04:31 +0000
@@ -0,0 +1,86 @@
+.. _psaas_utility_user:
+
+==============
+ Utility user
+==============
+
+|Percona Server| has implemented ability to have a |MySQL| user who has system access to do administrative tasks but limited access to user schema. This feature is especially useful to those operating |MySQL| As A Service. 
+
+This user has a mixed and special scope of abilities and protection:
+
+  * Utility user will not appear in the mysql.user table and can not be modified by any other user, including root.
+
+  * Utility user will not appear in USER_STATISTICS, CLIENT_STATISTICS or THREAD_STATISTICS tables.
+
+  * Utility user's queries may appear in the general and slow logs.
+
+  * Utility user doesn't have the ability create, modify, delete or see any schemas or data not specified (except for information_schema).
+
+  * Utility user may modify all visible, non read-only system variables (see :ref:`expanded_option_modifiers` functionality).
+
+  * Utility user may see, create, modify and delete other system users only if given access to the mysql schema.
+
+  * Regular users may be granted proxy rights to the utility user but any attempt to impersonate the utility user will fail. The utility user may not be granted proxy rights on any regular user. For example running: GRANT PROXY ON utility_user TO regular_user; will not fail, but any actual attempt to impersonate as the utility user will fail. Running: `GRANT PROXY ON regular_user TO utility_user;` will fail when utility_user is an exact match or is more specific than than the utility user specified.
+
+When the server starts, it will note in the log output that the utility user exists and the schemas that it has access to.
+
+In order to have the ability for a special type of MySQL user, which will have a very limited and special amount of control over the system and can not be see or modified by any other user including the root user, three new options have been added.
+
+Option :variable:`utility_user` specifies the user which the system will create and recognize as the utility user. The host in the utility user specification follows conventions described in the `MySQL manual <http://dev.mysql.com/doc/refman/5.5/en/connection-access.html>`_, i.e. it allows wildcards and IP masks. Anonymous user names are not permitted to be used for the utility user name.
+
+This user must not be an exact match to any other user that exists in the mysql.user table. If the server detects that the user specified with this option exactly matches any user within the mysql.user table on start up, the server will report an error and shut down gracefully. If host name wildcards are used and a more specific user specification is identified on start up, the server will report a warning and continue. 
+
+ Example: :option:`--utility_user` =frank@% and frank@localhost exists within the mysql.user table.
+
+If a client attempts to create a MySQL user that matches this user specification exactly or if host name wildcards are used for the utility user and the user being created has the same name and a more specific host, the creation attempt will fail with an error.
+
+ Example: :option:`--utility_user` =frank@% and CREATE USER 'frank@localhost';
+
+As a result of these requirements, it is strongly recommended that a very unique user name and reasonably specific host be used and that any script or tools test that they are running within the correct user by executing 'SELECT CURRENT_USER()' and comparing the result against the known utility user.
+
+Option :variable:`utility_user_password` specifies the password for the utility user and MUST be specified or the server will shut down gracefully with an error.
+
+ Example: :option:`--utility_user_password` =`Passw0rD`;
+
+Option :variable:`utility_user_schema_access` specifies the name(s) of the schema(s) that the utility user will have access to read write and modify. If a particular schema named here does not exist on start up it will be ignored. If a schema by the name of any of those listed in this option is created after the server is started, the utility user will have full access to it.
+
+ Example: :option:`--utility_user_schema_access` =schema1,schema2,schema3 ;
+
+System Variables
+================
+
+.. variable:: utility_user
+
+     :version 5.5.27-28.0: Implemented
+     :cli: No
+     :conf: utility_user=<user@host>
+     :scope: Global
+     :dyn: No
+     :vartype: String
+     :default: NULL
+
+Specifies a MySQL user that will be added to the internal list of users and recognized as the utility user.
+
+.. variable:: utility_user_password
+
+     :version 5.5.27-28.0: Implemented
+     :cli: No
+     :conf: utility_user_password=<password>
+     :scope: Global
+     :dyn: No
+     :vartype: String
+     :default: NULL
+
+Specifies the password required for the utility user.
+
+.. variable:: utility_user_schema_access
+
+     :version 5.5.27-28.0: Implemented
+     :cli: No
+     :conf: utility_user_schema_access=<schema>,<schema>,<schema>
+     :scope: Global
+     :dyn: No
+     :vartype: String
+     :default: NULL
+
+Specifies the schemas that the utility user has access to in a comma delimited list.

=== modified file 'doc/source/percona-theme/layout.html'
--- doc/source/percona-theme/layout.html	2012-07-18 06:25:14 +0000
+++ doc/source/percona-theme/layout.html	2012-08-22 15:04:31 +0000
@@ -214,7 +214,7 @@
       <div class="searchlink"><a onmouseover="SEARCH.Open()"><img id="searchlink-anchor" src="http://s2.percona.com/ui-search.png" alt="" /></a></div>
       <span class="inv"><![CDATA[<noindex>]]></span>
      	<div class="navicontainer"><div class="navi">
-		<span id="navilink-span-about-us" ><a id="navilink-a-about-us" href="/about-us/">About Us</a></span><span id="navilink-span-mysql-consulting" ><a id="navilink-a-mysql-consulting" href="/mysql-consulting/">Consulting</a></span><span id="navilink-span-support" ><a id="navilink-a-support" href="/mysql-support/">Support</a></span><span id="navilink-span-training" ><a id="navilink-a-training" href="/training/">Training</a></span><span id="navilink-span-development" ><a id="navilink-a-development" href="/development/">Development</a></span><span id="navilink-span-software" ><a id="navilink-a-software" href="/software/">Software</a></span><span id="navilink-span-events" ><a id="navilink-a-events" href="/live/">Events</a></span><span id="navilink-span-contact" ><a id="navilink-a-contact" href="/contact/">Contact Us</a></span>      
+		      
 		</div></div>
 
 		<span class="inv"><![CDATA[</noindex>]]></span>
@@ -329,39 +329,7 @@
 {%- endblock %}
 <span class="inv"><!--[CDATA[<noindex-->]]&gt;</span>
 <div id="submenus">
-	<div class="navi-dropdown" id="navi-dropdown-about-us">
-    <div class="navi-dropdown-header-l"><!-- //--></div>
-    <div class="navi-dropdown-content"><div class="item"><a href="/about-us/our-mission/">Our Mission</a></div><div class="item"><a href="/about-us/why-percona/">Why Percona?</a></div><div class="item"><a href="/about-us/procedures/">Coordinating with Percona</a></div><div class="item"><a href="/about-us/customers/">Customers</a></div><div class="item"><a href="/webinars/">Webinars</a></div><div class="item"><a href="/about-us/mysql-case-studies/">MySQL Case Studies</a></div><div class="item"><a href="/about-us/our-team/">Our Team</a></div><div class="item"><a href="/about-us/books/">Our Books</a></div><div class="item"><a href="/about-us/blogs/">Our Blogs</a></div><div class="item"><a href="/about-us/mysql-white-papers/">MySQL White Papers</a></div><div class="item"><a href="/about-us/conferences/">Conferences</a></div><div class="item"><a href="/about-us/presentations/">Presentations</a></div><div class="item"><a href="/about-us/newsletters/">Newsletters</a></div><div class="item"><a href="/about-us/pressreleases/">Press Releases</a></div><div class="item"><a href="/about-us/careers/">Careers</a></div>    </div>
-    <div class="navi-dropdown-footer"><!-- //--></div>
-  </div><div class="navi-dropdown" id="navi-dropdown-mysql-consulting">
-    <div class="navi-dropdown-header-l"><!-- //--></div>
-    <div class="navi-dropdown-content"><div class="item"><a href="/mysql-consulting/overview/">MySQL Consulting Overview</a></div><div class="item"><a href="/mysql-consulting/prices/">MySQL Consulting Prices</a></div><div class="item"><a href="/mysql-consulting/architecture/">MySQL Architecture &amp; Design</a></div><div class="item"><a href="/mysql-consulting/mysql-backups/">MySQL Backups</a></div><div class="item"><a href="/mysql-consulting/cloud-computing/">MySQL Cloud Solutions</a></div><div class="item"><a href="/mysql-consulting/cluster/">MySQL Cluster Consulting</a></div><div class="item"><a href="/mysql-consulting/data-warehousing/">MySQL Data Warehousing</a></div><div class="item"><a href="/mysql-consulting/data-recovery/">MySQL Data Recovery</a></div><div class="item"><a href="/mysql-consulting/high-availability/">MySQL High Availability</a></div><div class="item"><a href="/mysql-consulting/mysql-monitoring-graphing/">MySQL Monitoring &amp; Graphing</a></div><div class="item"><a href="/mysql-consulting/mysql-onsite-consulting/">MySQL Onsite Consulting</a></div><div class="item"><a href="/mysql-consulting/performance-audit/">MySQL Performance Audit</a></div><div class="item"><a href="/mysql-consulting/remote-dba/">MySQL Remote DBA</a></div><div class="item"><a href="/mysql-consulting/mysql-replication/">MySQL Replication</a></div><div class="item"><a href="/mysql-consulting/upgrade/">MySQL Version Upgrades</a></div><div class="item"><a href="/mysql-consulting/24x7-emergency/">Emergency 24&times;7 Consulting</a></div><div class="item"><a href="/mysql-consulting/migration/">Migration to MySQL</a></div><div class="item"><a href="/drizzle-consulting/">Drizzle Consulting</a></div><div class="item"><a href="/mysql-consulting/sphinx/">Sphinx Consulting</a></div><div class="item"><a href="/mysql-consulting/drbd/">DRBD Consulting</a></div><div class="item"><a href="/mysql-consulting/memcached/">Memcached Consulting</a></div><div class="item"><a href="/mysql-consulting/other-services/">Other Consulting Services</a></div>    </div>
-    <div class="navi-dropdown-footer"><!-- //--></div>
-  </div><div class="navi-dropdown" id="navi-dropdown-support">
-    <div class="navi-dropdown-header-l"><!-- //--></div>
-    <div class="navi-dropdown-content"><div class="item"><a href="/mysql-support/">MySQL Support Overview</a></div><div class="item"><a href="/prices/mysql-support/">MySQL Support Prices</a></div><div class="item"><a href="/mysql-support/policies/">MySQL Support Policies</a></div><div class="item"><a href="/mysql-support/consulting-vs-support/">Consulting vs. Support</a></div><div class="item"><a href="https://customers.percona.com">Customer Portal Login</a></div>    </div>
-    <div class="navi-dropdown-footer"><!-- //--></div>
-  </div><div class="navi-dropdown" id="navi-dropdown-training">
-    <div class="navi-dropdown-header-l"><!-- //--></div>
-    <div class="navi-dropdown-content"><div class="item"><a href="/training/">MySQL Training Overview</a></div><div class="item"><a href="/prices/training/">MySQL Training Prices</a></div><div class="item"><a href="/training/classes/dba/">MySQL DBA Training</a></div><div class="item"><a href="/training/classes/developers/">MySQL Developer Training</a></div><div class="item"><a href="/training/classes/operations/">MySQL Operations Training</a></div><div class="item"><a href="/training/classes/innodb/">InnoDB &amp; XtraDB Training</a></div><div class="item"><a href="/training/classes/custom-onsite/">Custom Onsite Training</a></div>    </div>
-    <div class="navi-dropdown-footer"><!-- //--></div>
-  </div><div class="navi-dropdown" id="navi-dropdown-development">
-    <div class="navi-dropdown-header-l"><!-- //--></div>
-    <div class="navi-dropdown-content"><div class="item"><a href="/development/mysql/">MySQL Development Overview</a></div><div class="item"><a href="/development/prices/">Custom Development Prices</a></div><div class="item"><a href="/development/maintenance/">MySQL Support Overview</a></div><div class="item"><a href="/development/benchmarking/">Custom Product Evaluation</a></div><div class="item"><a href="/development/maatkit/">Custom Maatkit Development</a></div><div class="item"><a href="/development/custom-tools/">Custom Tools Development</a></div>    </div>
-    <div class="navi-dropdown-footer"><!-- //--></div>
-  </div><div class="navi-dropdown" id="navi-dropdown-software">
-    <div class="navi-dropdown-header-l"><!-- //--></div>
-    <div class="navi-dropdown-content"><div class="item"><a href="/software/">Percona Software for MySQL</a></div><div class="item"><a href="/software/percona-server/">Percona Server with XtraDB</a></div><div class="item"><a href="/software/percona-xtradb-cluster/">Percona XtraDB Cluster</a></div><div class="item"><a href="/software/percona-xtrabackup/">Percona XtraBackup</a></div><div class="item"><a href="/software/mysql-innodb-data-recovery-tools/">Data Recovery Toolkit</a></div><div class="item"><a href="/software/percona-xtradb/">Percona XtraDB</a></div><div class="item"><a href="/software/percona-toolkit/">Percona Toolkit</a></div><div class="item"><a href="/software/percona-monitoring-plugins/">Percona Monitoring Plugins</a></div><div class="item"><a href="/prices/software/">Software Prices</a></div><div class="item"><a href="/downloads/">Downloads</a></div><div class="item"><a href="/software/repositories/">Repositories</a></div><div class="item"><a href="/software/documentation/">Documentation</a></div><div class="item"><a href="http://forum.percona.com">Forum</a></div><div class="item"><a href="http://groups.google.com/group/percona-discussion">Google Discussion</a></div><div class="item"><a href="https://launchpad.net/percona-server">Launchpad</a></div>    </div>
-    <div class="navi-dropdown-footer"><!-- //--></div>
-  </div><div class="navi-dropdown" id="navi-dropdown-events">
-    <div class="navi-dropdown-header-r"><!-- //--></div>
-    <div class="navi-dropdown-content"><div class="item"><a href="/live/nyc-2012/">New York 2012</a></div><div class="item"><a href="/live/london-2012/">London 2012</a></div><div class="item"><a href="/live/mysql-conference-2013/">MySQL Conference &amp; Expo 2013</a></div><div class="item"><a href="/live/mysql-conference-2012/">MySQL Conference &amp; Expo 2012</a></div><div class="item"><a href="/live/">Previous Percona Live Events</a></div>    </div>
-    <div class="navi-dropdown-footer"><!-- //--></div>
-  </div><div class="navi-dropdown" id="navi-dropdown-contact">
-    <div class="navi-dropdown-header-r"><!-- //--></div>
-    <div class="navi-dropdown-content"><div class="item"><a href="/contact/24x7-emergency/">24&times;7 Emergency</a></div><div class="item"><a href="/contact/sales/">Sales &amp; General Inquiries</a></div><div class="item"><a href="/contact/billing/">Billing Inquiries</a></div><div class="item"><a href="https://customers.percona.com">Customer Portal Login</a></div><div class="item"><a href="/contact/phone-directory/">Phone Directory</a></div><div class="item"><a href="/subscribe/">Subscribe to Newsletter</a></div>    </div>
-    <div class="navi-dropdown-footer"><!-- //--></div>
-  </div>
+	
   <div id="search-dropdown" class="search-dropdown">
     <div class="search-dropdown-header"><!-- //--></div>
     <div class="search-dropdown-content">
@@ -383,7 +351,7 @@
 <!-- /GA //-->
 <!-- NAVI //-->
 <script type="text/javascript">//<![CDATA[
-var navi = [{id:"about-us", direction: "l"},{id:"mysql-consulting", direction: "l"},{id:"support", direction: "l"},{id:"training", direction: "l"},{id:"development", direction: "l"},{id:"software", direction: "l"},{id:"events", direction: "r"},{id:"contact", direction: "r"}];
+var navi = [];
 for(var i = 0, c = navi.length; i < c; i++) {
 window.jQuery('#navilink-a-' + navi[i].id).bind('mouseover',{id: navi[i].id, direction:navi[i].direction}, function(e) { NAVI.Open(e.data.id, e.data.direction); } );
 }

=== added file 'doc/source/release-notes/Percona-Server-5.5.27-28.0.rst'
--- doc/source/release-notes/Percona-Server-5.5.27-28.0.rst	1970-01-01 00:00:00 +0000
+++ doc/source/release-notes/Percona-Server-5.5.27-28.0.rst	2012-08-22 15:04:31 +0000
@@ -0,0 +1,38 @@
+.. rn:: 5.5.27-28.0
+
+===============================
+ |Percona Server| 5.5.27-28.0
+===============================
+
+Percona is glad to announce the release of |Percona Server| 5.5.27-28.0 on August 23rd, 2012 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.5/Percona-Server-5.5.27-28.0/>`_ and from the `Percona Software Repositories <http://www.percona.com/docs/wiki/repositories:start>`_).
+
+Based on `MySQL 5.5.27 <http://dev.mysql.com/doc/refman/5.5/en/news-5-5-27.html>`_, including all the bug fixes in it, |Percona Server| 5.5.27-28.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.27-28.0 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.5.27-28.0>`_. 
+
+Bug fix for bug :bug:`1007268` has been targeted for the next |Percona Server| release. Workaround for this bug exists and it's setting up the :variable:`innodb_lazy_drop_table` to 1.
+
+New Features
+============
+
+  * |Percona Server| supports tunable buffer size for fast index creation in |InnoDB|. This value was calculated based on the merge block size (which was hardcoded to 1 MB) and the minimum index record size. By adding the session variable :variable:`innodb_merge_sort_block_size` block size that is used in the merge sort can now be adjusted for better performance.
+
+  * |Percona Server| has implemented ability to have a MySQL :ref:`psaas_utility_user` who has system access to do administrative tasks but limited access to user schema. This feature is especially useful to those operating MySQL As A Service.
+
+  * New :ref:`expanded_option_modifiers` have been added to allow access control to system variables.
+
+  * New table :table:`INNODB_UNDO_LOGS` has been added to allow access to undo segment information. Each row represents an individual undo segment and contains information about which rollback segment the undo segment is currently owned by, which transaction is currently using the undo segment, and other size and type information for the undo segment. This information is 'live' and calculated for each query of the table.
+
+Bug Fixes
+=========
+
+  * Fixed incorrect merge of MySQL bug `#61188 <http://bugs.mysql.com/bug.php?id=61188>`_ fix which caused server to freeze with "has waited at buf0buf.c line 2529 for XXX seconds the semaphore" errors. This regression was introduced in |Percona Server| 5.5.23-25.3. Bug fixed :bug:`1026926` (*Stewart Smith*).
+
+  * Fixed regression introduced in |Percona Server| 5.5.23-25.3 when merging the upstream fix for MySQL bug `#64284 <http://bugs.mysql.com/bug.php?id=64284>`_. Bug fixed :bug:`1015109` (*Stewart Smith*).
+
+  * Fixed the upstream MySQL bug `#66301 <http://bugs.mysql.com/bug.php?id=66301>`_. Concurrent INSERT ... ON DUPLICATE KEY UPDATE statements on a table with an AUTO_INCREMENT column could result in spurious duplicate key errors (and, as a result, lost data due to some rows being updated rather than inserted) with the default value of innodb_autoinc_lock_mode=1. Bug fixed :bug:`1035225` (*Alexey Kopytov*).
+
+  * Removed error log warnings that occured after enabling :variable:`innodb_use_sys_stats_table` and before ANALYZE TABLE is run for each table. Bug fixed :bug:`890623` (*Alexey Kopytov*).
+
+  * Removed the unneeded lrusort.py script. The server now does this sorting automatically and has done for some time. Bug fixed :bug:`882653` (*Stewart Smith*).
+
+  * Fixed the malformed CHANGE MASTER query in the output of ``mysqldump`` with :option:`--include-master-host-port` option. Bug fixed :bug:`1013432` (*Stewart Smith*).
+