summaryrefslogtreecommitdiff
path: root/storage
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2022-02-03 12:18:14 +0200
committerOleksandr Byelkin <sanja@mariadb.com>2022-02-03 17:02:14 +0100
commit05c33d6216ab125b964be54701f474bcf445241e (patch)
tree3186e81adbd99e15dfbd7a7f1f458513f32cb235 /storage
parentf5c5f8e41ecd4d407022d3772ac43075c16824a5 (diff)
downloadmariadb-git-05c33d6216ab125b964be54701f474bcf445241e.tar.gz
MDEV-27736 Allow seamless upgrade despite ROW_FORMAT=COMPRESSED
In commit 9bc874a594edbc0e124131d0ff30b44f5fade52d (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. 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.
Diffstat (limited to 'storage')
-rw-r--r--storage/innobase/handler/ha_innodb.cc4
1 files changed, 2 insertions, 2 deletions
diff --git a/storage/innobase/handler/ha_innodb.cc b/storage/innobase/handler/ha_innodb.cc
index 31a1f477759..bfb3075edc6 100644
--- a/storage/innobase/handler/ha_innodb.cc
+++ b/storage/innobase/handler/ha_innodb.cc
@@ -19615,8 +19615,8 @@ static MYSQL_SYSVAR_BOOL(read_only, srv_read_only_mode,
static MYSQL_SYSVAR_BOOL(read_only_compressed, innodb_read_only_compressed,
PLUGIN_VAR_OPCMDARG,
- "Make ROW_FORMAT=COMPRESSED tables read-only (ON by default)",
- NULL, NULL, TRUE);
+ "Make ROW_FORMAT=COMPRESSED tables read-only",
+ NULL, NULL, FALSE);
static MYSQL_SYSVAR_BOOL(cmp_per_index_enabled, srv_cmp_per_index_enabled,
PLUGIN_VAR_OPCMDARG,