khanh.pndc/nextcloud-docs
1
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2026-01-03 02:09:45 +07:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #13449 from nextcloud/fix/admin_manual--release_notes--upgrade-31--db

Browse Source 
fix(admin_manual/release_notes): correct ROW FORMAT migration in 31
This commit is contained in:
Daniel
2025-07-25 21:49:54 +02:00
committed by GitHub
parent 67ef7cd5bb 7d0d0740ed
commit fcb3ec4a3b
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
admin_manual/release_notes/upgrade_to_31.rst
View File

@@ -14,8 +14,10 @@ Database configuration
Other row formats than ``DYNAMIC`` for MySQL and MariaDB databases will `issue a warning since Nextcloud 24 <https://github.com/nextcloud/server/issues/34497>`_,
as they often cause performance issues.
With Nextcloud 31 a `more prominent new setup warning <https://github.com/nextcloud/server/pull/48547>`_ for this was added.
To resolve the warning, in most cases running ``occ db:convert-mysql-charset`` will resolve the issue.
If some tables are not covered by the ``occ`` command, issuing the proper ``ALTER TABLE`` DDL commands to change the row format during a maintenance window is needed.
The row format can be changed via ``ALTER TABLE`` DDL commands during a maintenance window.
Changing the row format from ``COMPRESSED`` to ``DYNAMIC`` requires about 2x the disk space and may take a long time depending on the size of the database.
See the `MySQL documentation <https://dev.mysql.com/doc/refman/en/innodb-row-format.html>`_ for more information.
If you're not sure how to do this, you can `find some tips and tricks from the community <https://help.nextcloud.com/t/upgrade-to-nextcloud-hub-10-31-0-0-incorrect-row-format-found-in-your-database/218366/>`_.
PHP configuration