[Pkg-owncloud-commits] [owncloud-doc] 29/56: Backport #1844 to stable8.2

[David Prévot]

This is an automated email from the git hooks/post-receive script.

taffit pushed a commit to branch stable8
in repository owncloud-doc.

commit 55f9a7deabcc15354d10b0efe4f0fe37b6a2a2af
Author: RealRancor <Fisch.666 at gmx.de>
Date:   Sat Oct 31 19:48:25 2015 +0100

    Backport #1844 to stable8.2
---
 .../linux_database_configuration.rst               | 31 ++++++++++++++++++++++
 admin_manual/installation/linux_installation.rst   |  5 +++-
 admin_manual/maintenance/upgrade.rst               | 12 +--------
 3 files changed, 36 insertions(+), 12 deletions(-)

diff --git a/admin_manual/configuration_database/linux_database_configuration.rst b/admin_manual/configuration_database/linux_database_configuration.rst
index c1c5bf7..2ad65c8 100644
--- a/admin_manual/configuration_database/linux_database_configuration.rst
+++ b/admin_manual/configuration_database/linux_database_configuration.rst
@@ -17,6 +17,37 @@ Choosing to use MySQL / MariaDB, PostgreSQL, or Oracle as your database requires
 
 .. note:: The steps for configuring a third party database are beyond the scope of this document.  Please refer to the documentation for your specific database choice for instructions.
 
+.. _db-binlog-label:
+
+MySQL / MariaDB with Binary Logging Enabled
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+ownCloud is currently using a ``TRANSACTION_READ_COMMITTED`` transaction isolation
+to avoid data loss under high load scenarios (e.g. by using the sync client with
+many clients/users and many parallel operations). This requires a disabled or
+correctly configured binary logging when using MySQL or MariaDB. Your system is
+affected if you see the following in your log file during the installation or
+update of ownCloud:
+
+ An unhandled exception has been thrown:
+ exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 1665 
+ Cannot execute statement: impossible to write to binary log since 
+ BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited 
+ to row-based logging. InnoDB is limited to row-logging when transaction 
+ isolation level is READ COMMITTED or READ UNCOMMITTED.'
+
+There are two solutions. One is to disable binary logging. Binary logging 
+records all changes to your database, and how long each change took. The 
+purpose of binary logging is to enable replication and to support backup 
+operations.
+
+The other is to change the BINLOG_FORMAT = STATEMENT in your database 
+configuration file, or possibly in your database startup script, to 
+BINLOG_FORMAT = MIXED. See `Overview of the Binary 
+Log <https://mariadb.com/kb/en/mariadb/overview-of-the-binary-log/>`_ and `The 
+Binary Log <https://dev.mysql.com/doc/refman/5.6/en/binary-log.html>`_ for 
+detailed information.
+
 Parameters
 ----------
 For setting up ownCloud to use any database, use the instructions in :doc:`../installation/installation_wizard`. You should not have to edit the respective values in the :file:`config/config.php`.  However, in special cases (for example, if you want to connect your ownCloud instance to a database created by a previous installation of ownCloud), some modification might be required.
diff --git a/admin_manual/installation/linux_installation.rst b/admin_manual/installation/linux_installation.rst
index 87f168c..62163c1 100644
--- a/admin_manual/installation/linux_installation.rst
+++ b/admin_manual/installation/linux_installation.rst
@@ -70,4 +70,7 @@ options.
 
 **Running ownCloud in a subdir**: If you're running ownCloud in a subdir and
 want to use CalDAV or CardDAV clients make sure you have configured the correct 
-:ref:`service-discovery-label` URLs.
\ No newline at end of file
+:ref:`service-discovery-label` URLs.
+
+**Note for MySQL/MariaDB environments**: Please refer to :ref:`db-binlog-label`
+on how to correctly configure your environment if you have binary logging enabled.
\ No newline at end of file
diff --git a/admin_manual/maintenance/upgrade.rst b/admin_manual/maintenance/upgrade.rst
index 2ddfdd1..5e913cb 100644
--- a/admin_manual/maintenance/upgrade.rst
+++ b/admin_manual/maintenance/upgrade.rst
@@ -261,17 +261,7 @@ enabled, your upgrade may fail with these errors in your MySQL/MariaDB log::
  to row-based logging. InnoDB is limited to row-logging when transaction 
  isolation level is READ COMMITTED or READ UNCOMMITTED.' 
 
-There are two solutions. One is to disable binary logging. Binary logging 
-records all changes to your database, and how long each change took. The 
-purpose of binary logging is to enable replication and to support backup 
-operations.
-
-The other is to change the BINLOG_FORMAT = STATEMENT in your database 
-configuration file, or possibly in your database startup script, to 
-BINLOG_FORMAT = MIXED. See `Overview of the Binary 
-Log <https://mariadb.com/kb/en/mariadb/overview-of-the-binary-log/>`_ and `The 
-Binary Log <https://dev.mysql.com/doc/refman/5.6/en/binary-log.html>`_ for 
-detailed information.
+Please refer to :ref:`db-binlog-label` on how to correctly configure your environment.
 
 Occasionally, *files do not show up after a upgrade*. A rescan of the files can help::
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-owncloud/owncloud-doc.git