遇到的mysql bug

最新推荐文章于 2025-06-20 14:58:25 发布

原创最新推荐文章于 2025-06-20 14:58:25 发布 · 517 阅读

0 ·

CC 4.0 BY-SA版权

MySQL管理专栏收录该内容

51 篇文章

订阅专栏

本文探讨了MySQL 5.7版本中InnoDB表的CREATE_TIME和UPDATE_TIME列显示时间戳的变化。此前对于分区的InnoDB表，CREATE_TIME总是显示为NULL值，而在5.7.8及以后版本中得到了修正。同样，UPDATE_TIME列在5.7.2版本开始显示最后一次更新的时间戳。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

mysql版本5.5，在information_schema下的tables表时，发现create_time这列是空值，百思不得其解，后查询官方文档如下：

Prior to MySQL 5.7.8, for partitioned InnoDB tables, the CREATE_TIME column always showedNULL. This column shows the correct table creation time for such tables in MySQL 5.7.8 and later. (Bug #17299181, Bug #69990)
Beginning with MySQL 5.7.2, UPDATE_TIME displays a timestamp value for the lastUPDATE, INSERT, or DELETE performed on InnoDB tables that are not partitioned. Previously,UPDATE_TIME displayed a NULL value for InnoDB tables. For MVCC, the timestamp value reflects the COMMIT time, which is considered the last update time. Timestamps are not persisted when the server is restarted or when the table is evicted from theInnoDB data dictionary cache.

The UPDATE_TIME column also shows this information for partitionedInnoDB tables in MySQL 5.7.8 and later. Previously this column was alwaysNULL for such tables. (Bug #17299181, Bug #69990)