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

[Hrvoje Matijakovic]

[Laurynas Biveinis (laurynas-biveinis)]

    - s/partition tables/partitioned tables
    - For the debian-sys-maint answer, add a sentence on the end "For
      more information how to setup a replication slave using
      XtraBackup see ..."
    - In the title of that question s/make/setup
    - s/but it is skipped for all log files writes/but not the log files.

review: Needs Fixing

[Laurynas Biveinis (laurynas-biveinis)]

review: Approve

=== modified file 'doc/source/diagnostics/user_stats.rst'
--- doc/source/diagnostics/user_stats.rst	2012-12-10 14:01:11 +0000
+++ doc/source/diagnostics/user_stats.rst	2013-09-30 15:53:59 +0000
@@ -109,6 +109,9 @@
   | mysql        | tables_priv           | PRIMARY            |         2 |
   +--------------+-----------------------+--------------------+-----------+
 
+.. note:: 
+
+   Current implementation of index statistics doesn't support partitioned tables.
 
 
 .. table:: INFORMATION_SCHEMA.TABLE_STATISTICS
@@ -131,6 +134,9 @@
   | mysql        | tables_priv                   |         2 |            0 |                      0 | 
   +--------------+-------------------------------+-----------+--------------+------------------------+
 
+.. note:: 
+
+   Current implementation of table statistics doesn't support partitioned tables.
 
 .. table:: INFORMATION_SCHEMA.THREAD_STATISTICS
 
 
=== modified file 'doc/source/faq.rst'
--- doc/source/faq.rst	2011-09-26 22:51:08 +0000
+++ doc/source/faq.rst	2013-09-30 15:53:59 +0000
@@ -18,3 +18,8 @@
 ===================================================
 
 A: No, you don't need to change anything on the clients. |Percona Server| is 100% compatible with all existing client libraries and connectors.
+
+Q: When using the |Percona XtraBackup| to setup a replication slave on Debian based systems I'm getting: "ERROR 1045 (28000): Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)" 
+=========================================================================================================================================================================================================
+
+A: In case you're using init script on Debian based system to start ``mysqld``, be sure that the password for ``debian-sys-maint`` user has been updated and it's the same as that user's password from the server that the backup has been taken from. Password can be seen and updated in :file:`/etc/mysql/debian.cnf`. For more information on how to set up a replication slave using |Percona XtraBackup| see `this how-to <http://www.percona.com/doc/percona-xtrabackup/2.1/howtos/setting_up_replication.html>`_.
 
=== modified file 'doc/source/scalability/innodb_io.rst'
--- doc/source/scalability/innodb_io.rst	2013-01-30 09:27:00 +0000
+++ doc/source/scalability/innodb_io.rst	2013-09-30 15:53:59 +0000
@@ -151,9 +151,9 @@
     Use ``O_SYNC`` to open and flush the log files; use ``fsync()`` to flush the data files.
 
   * ``O_DIRECT``: 
-    Use ``O_DIRECT`` (or ``directio()`` on Solaris) to open the data files; use ``fsync()`` to flush both the data and log files.
+    Use ``O_DIRECT`` to open the data files and ``fsync()`` system call to flush both the data and log files.
 
-  * ``ALL_O_DIRECT``: use ``O_DIRECT`` open and flush both the data and the log files. This option is recommended when |InnoDB| log files are big (more than 8GB), otherwise there might be even a performance degradation. **Note**: When using this option on *ext4* filesystem variable :variable:`innodb_log_block_size` should be set to 4096 (default log-block-size in *ext4*) in order to avoid the ``unaligned AIO/DIO`` warnings.
+  * ``ALL_O_DIRECT``: use ``O_DIRECT`` to open both data and log files, and use ``fsync()`` to flush the data files but not the log files. This option is recommended when |InnoDB| log files are big (more than 8GB), otherwise there might be even a performance degradation. **Note**: When using this option on *ext4* filesystem variable :variable:`innodb_log_block_size` should be set to 4096 (default log-block-size in *ext4*) in order to avoid the ``unaligned AIO/DIO`` warnings.
 
 
 .. variable:: innodb_flush_neighbor_pages