[MDEV-17160] InnoDB produces wrong message or wrong row format upon attempt to create table with ROW_FORMAT=COMPRESSED and big page size Created: 2018-09-09  Updated: 2018-09-10

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.1
Fix Version/s: 10.1

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-14904 Please backport `innodb_default_row_f... Closed

 Description   

--source include/have_innodb.inc
 
SET @file_format= @@innodb_file_format;
SET GLOBAL innodb_file_format= Barracuda;
 
CREATE TABLE t1 (a INT) ENGINE=InnoDB ROW_FORMAT=COMPRESSED;
SHOW WARNINGS;
query_vertical SHOW TABLE STATUS LIKE 't1';
 
# Cleanup
DROP TABLE t1;
SET GLOBAL innodb_file_format= @file_format;

10.1 f1bcfbb4373

CREATE TABLE t1 (a INT) ENGINE=InnoDB ROW_FORMAT=COMPRESSED;
Warnings:
Warning	1478	InnoDB: Cannot create a COMPRESSED table when innodb_page_size > 16k. Assuming ROW_FORMAT=COMPACT.
 
SHOW TABLE STATUS LIKE 't1';
Name	t1
Engine	InnoDB
Version	10
Row_format	Dynamic
...

So, the warning says that the assumed format is COMPACT, but the created table has format Dynamic (or pretends to, see MDEV-17161).



 Comments   
Comment by Marko Mäkelä [ 2018-09-10 ]

Note that since MDEV-14904 Backport innodb_default_row_format
also MariaDB 10.1 could implicitly use ROW_FORMAT=DYNAMIC. But the default value in 10.1 should be innodb_default_row_format=compact.

Generated at Thu Feb 08 08:34:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.