Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit b74354e

Browse files
committed
remove wrong database-guide
Signed-off-by: Marius Blüm <[email protected]>
1 parent 72d6e27 commit b74354e

File tree

1 file changed

+4
-35
lines changed

1 file changed

+4
-35
lines changed

admin_manual/configuration_database/linux_database_configuration.rst

Lines changed: 4 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -20,37 +20,6 @@ requires that you install and set up the server software first.
2020
scope of this document. Please refer to the documentation for your specific
2121
database choice for instructions.
2222

23-
.. _db-binlog-label:
24-
25-
MySQL / MariaDB with Binary Logging Enabled
26-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
27-
28-
Nextcloud is currently using a ``TRANSACTION_READ_COMMITTED`` transaction isolation
29-
to avoid data loss under high load scenarios (e.g. by using the sync client with
30-
many clients/users and many parallel operations). This requires a disabled or
31-
correctly configured binary logging when using MySQL or MariaDB. Your system is
32-
affected if you see the following in your log file during the installation or
33-
update of Nextcloud:
34-
35-
An unhandled exception has been thrown:
36-
exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 1665
37-
Cannot execute statement: impossible to write to binary log since
38-
BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited
39-
to row-based logging. InnoDB is limited to row-logging when transaction
40-
isolation level is READ COMMITTED or READ UNCOMMITTED.'
41-
42-
There are two solutions. One is to disable binary logging. Binary logging
43-
records all changes to your database, and how long each change took. The
44-
purpose of binary logging is to enable replication and to support backup
45-
operations.
46-
47-
The other is to change the BINLOG_FORMAT = STATEMENT in your database
48-
configuration file, or possibly in your database startup script, to
49-
BINLOG_FORMAT = MIXED. See `Overview of the Binary
50-
Log <https://mariadb.com/kb/en/mariadb/overview-of-the-binary-log/>`_ and `The
51-
Binary Log <https://dev.mysql.com/doc/refman/5.6/en/binary-log.html>`_ for
52-
detailed information.
53-
5423
.. _db-transaction-label:
5524

5625
Database "READ COMMITED" transaction isolation level
@@ -176,7 +145,7 @@ You can quit the prompt by entering::
176145

177146
An Nextcloud instance configured with PostgreSQL would contain the path to the socket on
178147
which the database is running as the hostname, the system username the PHP process is using,
179-
and an empty password to access it, and the name of the database. The :file:`config/config.php` as
148+
and an empty password to access it, and the name of the database. The :file:`config/config.php` as
180149
created by the :doc:`../installation/installation_wizard` would therefore contain entries like
181150
this:
182151

@@ -240,9 +209,9 @@ Troubleshooting
240209
How to workaround General error: 2006 MySQL server has gone away
241210
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
242211

243-
The database request takes too long and therefore the MySQL server times out. Its
244-
also possible that the server is dropping a packet that is too large. Please
245-
refer to the manual of your database for how to raise the configuration options
212+
The database request takes too long and therefore the MySQL server times out. Its
213+
also possible that the server is dropping a packet that is too large. Please
214+
refer to the manual of your database for how to raise the configuration options
246215
``wait_timeout`` and/or ``max_allowed_packet``.
247216

248217
Some shared hosters are not allowing the access to these config options. For such

0 commit comments

Comments
 (0)