From 1cac35657e7c2c963bdbaf89bbc51e8a3d02ddb6 Mon Sep 17 00:00:00 2001 From: "Grigorii K. Shartsev" Date: Fri, 25 Jul 2025 15:30:52 +0200 Subject: [PATCH] fix(admin_manual/release_notes): correct ROW FORMAT migration in 31 Signed-off-by: Grigorii K. Shartsev --- admin_manual/release_notes/upgrade_to_31.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/admin_manual/release_notes/upgrade_to_31.rst b/admin_manual/release_notes/upgrade_to_31.rst index ce00d4e6f5f..324439bed29 100644 --- a/admin_manual/release_notes/upgrade_to_31.rst +++ b/admin_manual/release_notes/upgrade_to_31.rst @@ -14,8 +14,10 @@ Database configuration Other row formats than ``DYNAMIC`` for MySQL and MariaDB databases will `issue a warning since Nextcloud 24 `_, as they often cause performance issues. With Nextcloud 31 a `more prominent new setup warning `_ 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 `_ for more information. If you're not sure how to do this, you can `find some tips and tricks from the community `_. PHP configuration