innodb.row_size_error_log_warnings_3 '4k,innodb' w2 [ fail ]

        Test ended at 2023-03-20 15:37:05

CURRENT_TEST: innodb.row_size_error_log_warnings_3

mysqltest: At line 49: query 'CREATE TABLE t1(

f1 INT, f2 CHAR(200), f3 CHAR(200),

f4 CHAR(200), f5 CHAR(200), f6 CHAR(200),

f7 CHAR(200), f8 CHAR(200), f9 CHAR(200),

f10 CHAR(200), PRIMARY KEY(f1, f2(20), f3(20), f4(20))

) ROW_FORMAT=COMPRESSED, ENGINE=InnoDB' failed: ER_TOO_BIG_ROWSIZE (1118): Row size too large (> 1982). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.

The result from queries just before the failure was:

< snip >

test.t1	optimize	note	Table does not support optimize, doing recreate + analyze instead

test.t1	optimize	status	OK

Warnings:

Warning	139	Row size too large (> NNNN). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.

ALTER TABLE t1 FORCE;

Warnings:

Warning	139	Row size too large (> NNNN). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.

DROP TABLE t1;

SET @@global.log_warnings = 2;

#

# MDEV-20194 Warnings inconsistently issued upon CHECK on

#		table from older versions

#

set global innodb_compression_level=1;

CREATE TABLE t1(

f1 INT, f2 CHAR(200), f3 CHAR(200),

f4 CHAR(200), f5 CHAR(200), f6 CHAR(200),

f7 CHAR(200), f8 CHAR(200), f9 CHAR(200),

f10 CHAR(200), PRIMARY KEY(f1, f2(20), f3(20), f4(20))

) ROW_FORMAT=COMPRESSED, ENGINE=InnoDB;

More results from queries before failure can be found in /<<PKGBUILDDIR>>/builddir/mysql-test/var/2/log/row_size_error_log_warnings_3.log

 - skipping '/<<PKGBUILDDIR>>/builddir/mysql-test/var/2/log/innodb.row_size_error_log_warnings_3-4k,innodb/'

Retrying test innodb.row_size_error_log_warnings_3, attempt(2/3)...

innodb.innodb-alter-nullable '16k,innodb' w3 [ pass ]    233

worker[2] > Restart  - not started

***Warnings generated in error logs during shutdown after running tests: innodb.row_size_error_log_warnings_3 innodb.check_ibd_filesize

2023-03-20 15:37:04 8 [Warning] InnoDB: Cannot add field `col_3` in table `test`.`t1` because after adding it, the row size is 2396 which is greater than maximum allowed size (1982 bytes) for a record on index leaf page.

2023-03-20 15:37:04 8 [Warning] InnoDB: Cannot add field `col_3` in table `test`.`t1` because after adding it, the row size is 2396 which is greater than maximum allowed size (1982 bytes) for a record on index leaf page.

2023-03-20 15:37:04 8 [Warning] InnoDB: Cannot add field `col_3` in table `test`.`#sql-alter-3643a-8` because after adding it, the row size is 2396 which is greater than maximum allowed size (1982 bytes) for a record on index leaf page.

2023-03-20 15:37:04 8 [Warning] InnoDB: Cannot add field `col_3` in table `test`.`#sql-alter-3643a-8` because after adding it, the row size is 2396 which is greater than maximum allowed size (1982 bytes) for a record on index leaf page.

2023-03-20 15:37:04 8 [Warning] InnoDB: Cannot add field `col_3` in table `test`.`t1` because after adding it, the row size is 2396 which is greater than maximum allowed size (1982 bytes) for a record on index leaf page.

2023-03-20 15:37:04 8 [Warning] InnoDB: Cannot add field `col_3` in table `test`.`#sql-alter-3643a-8` because after adding it, the row size is 2396 which is greater than maximum allowed size (1982 bytes) for a record on index leaf page.

2023-03-20 15:37:04 8 [Warning] InnoDB: Cannot add field `col_3` in table `test`.`#sql-alter-3643a-8` because after adding it, the row size is 2396 which is greater than maximum allowed size (1982 bytes) for a record on index leaf page.

2023-03-20 15:37:04 8 [ERROR] InnoDB: Cannot add field `f9` in table `test`.`t1` because after adding it, the row size is 1680 which is greater than maximum allowed size (1583 bytes) for a record on index leaf page.