[MDEV-27736] Allow seamless upgrade despite ROW_FORMAT=COMPRESSED Created: 2022-02-03  Updated: 2022-03-22  Resolved: 2022-02-03

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.6, 10.7, 10.8
Fix Version/s: 10.6.6, 10.7.2, 10.8.1

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 1
Labels: regression-10.6

Issue Links:
Problem/Incident
is caused by MDEV-23497 make ROW_FORMAT=COMPRESSED read-only ... Closed

 Description   

In MDEV-23497, the configuration option innodb_read_only_compressed was introduced to giver users advance notice of a plan to remove ROW_FORMAT=COMPRESSED support for InnoDB.

The next step of this plan would have been to remove write support for ROW_FORMAT=COMPRESSED tables (MDEV-22367). Based on user feedback, this plan has been scrapped. Even though ROW_FORMAT=COMPRESSED is a dead end and causes some overhead for InnoDB data structures, we can live with that.

Now that we know that some users really want to keep using ROW_FORMAT=COMPRESSED, the previous default value of the parameter innodb_read_only_compressed=ON should be changed to OFF, to allow smooth upgrades to 10.6 and later versions, without requiring users to update any configuration file.


Generated at Thu Feb 08 09:55:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.