LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Heads up: MariaDB 10.6 breaking change (https://www.linuxquestions.org/questions/slackware-14/heads-up-mariadb-10-6-breaking-change-4175694396/)

cycojesus 04-28-2021 04:54 AM
Heads up: MariaDB 10.6 breaking change
 
Quote:
From MariaDB 10.6.0, tables that are of the COMPRESSED row format are read-only by default. This is the first step towards removing write support and deprecating the feature.
Latest mariadb upgrade in -current (10.6.0) broke my nextcloud and I had to revert to 10.5.9 (Thanks slackware.uk cumulative!!) while I think/explore/wait for a solution.

Here's a link to an issue stating the cause: https://github.com/nextcloud/server/issues/25436

cycojesus 04-28-2021 05:18 AM
Working solution I found for now until the feature is actually deprecated: pass --skip-innodb-read-only-compressed in rc.mysqld, line 45

avian 04-28-2021 05:44 AM
Thanks for the heads up, Im still on mariadb 10.5.9 but will probably need to apply the fix myself once the local slackware mirror updates with todays changes. Are you on nextcloud 21.0.1 ?

LuckyCyborg 04-28-2021 06:29 AM
Heads up! You shall remove the usage of this feature, because it is on the death row, waiting for its termination!

https://mariadb.com/kb/en/innodb-compressed-row-format/
Quote:
From MariaDB 10.6.0, tables that are of the COMPRESSED row format are read-only by default. This is the first step towards removing write support and deprecating the feature.

Set the innodb_read_only_compressed variable to OFF to make the tables writable.

avian 04-28-2021 07:45 AM
Quote:
Originally Posted by LuckyCyborg (Post 6245814)
Heads up! You shall remove the usage of this feature, because it is on the death row, waiting for its termination!
Yep, nextcloud is generally pretty good at this stuff, so I'd expect an upcoming version to include an occ maintenance option that will change row_format. Although a part of me is really tempted to change it now, after having checked to see that every single table is using compressed here.

Code:
MariaDB [nextcloud]> SELECT `table_name`, `row_format` FROM `information_schema`.`tables` WHERE `table_schema`=DATABASE();
table_name        row_format
oc_maps_devices        Compressed
oc_share        Compressed
oc_federated_reshares        Compressed
oc_dav_cal_proxy        Compressed
oc_maps_address_geo        Compressed
oc_authtoken        Compressed
oc_addressbookchanges        Compressed
oc_calendarobjects_props        Compressed
oc_webauthn        Compressed
oc_files_trash        Compressed
oc_comments_read_markers        Compressed
oc_preferences        Compressed
oc_vcategory        Compressed
[...]
[...]

cycojesus 04-28-2021 07:50 AM
Quote:
Originally Posted by avian (Post 6245806)
Thanks for the heads up, Im still on mariadb 10.5.9 but will probably need to apply the fix myself once the local slackware mirror updates with todays changes. Are you on nextcloud 21.0.1 ?
yes, 21.0.1

Quote:
Originally Posted by LuckyCyborg (Post 6245814)
Heads up! You shall remove the usage of this feature, because it is on the death row, waiting for its termination!

https://mariadb.com/kb/en/innodb-compressed-row-format/
I know, it's in the link I mention but I think I'll let the Nextcloud team deal with this as I haven't touched php for more than 15 years.

avian 04-28-2021 08:31 AM
Probably not the smartest move, but I altered the ROW_FORMAT to DYNAMIC for every nextcloud table. Upgraded to 10.6.0 and nextcloud seems satisfied (for now). No idea about long term consequences, so not exactly recommending this as a solution to others, more for the curious.

pipeweed 04-28-2021 08:33 AM
To follow the progress of deprecating/removing this feature on MariaDB's issue tracker, see https://jira.mariadb.org/browse/MDEV-22367


All times are GMT -5. The time now is 04:07 PM.