SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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 ?
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.
Last edited by LuckyCyborg; 04-28-2021 at 06:30 AM.
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.
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
Heads up! You shall remove the usage of this feature, because it is on the death row, waiting for its termination!
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.