[MDEV-13360] too long values in mysql.innodb_table_stats.table_name - Jira

XML

Word

Printable

Type: Bug
Status: Stalled (View Workflow)
Priority: Minor
Resolution: Unresolved
Affects Version/s: 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL), 11.4, 11.5(EOL), 11.6(EOL), 11.7, 11.8
Fix Version/s: 10.5, 10.6, 10.11, 11.4
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Labels:
- upstream
- upstream-fixed

create table extralongname_extralongname_extralongname_extralongname_ext (

  id int(10) unsigned not null,

  created_date date not null,

  created timestamp not null,

  primary key (created,id,created_date)

) engine=innodb stats_persistent=1 default charset=latin1

  partition by range (year(created_date))

  subpartition by hash (month(created_date))

  subpartitions 2 (

    partition p2007 values less than (2008),

    partition p2008 values less than (2009)

);

select length(table_name) from mysql.innodb_table_stats;

The last statement returns 79, even though the column is defined as varchar(64).

This can potentially fail in the upper layer in many different ways. For example, it makes copying ALTER TABLE to fail with "duplicate key value".

The same applies to innodb_index_stats too.

causes

MDEV-13274 mysql_upgrade fails if dbname+tablename+partioname > 64 chars

relates to

MDEV-14637 Latching order violation during btr_cur_pessimistic_delete()

MDEV-15020 Server hangs due to InnoDB persistent statistics or innodb_stats_auto_recalc

links to

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.