Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-8940

CREATE_TIME column of INFORMATION_SCHEMA.TABLES does not always update for innodb tables

    XMLWordPrintable

Details

    Description

      The CREATE_TIME column of INFORMATION_SCHEMA.TABLES does not always update for innodb tables when the table is dropped and recreated.

      Welcome to the MariaDB monitor.  Commands end with ; or \g.
      Your MariaDB connection id is 18
      Server version: 10.0.21-MariaDB mariadb.org binary distribution
       
      Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others.
       
      Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
       
      MariaDB [(none)]> create database xyz;
      Query OK, 1 row affected (0.00 sec)
       
      MariaDB [(none)]> use xyz
      Database changed
      MariaDB [xyz]> create table ct_test(id int);
      Query OK, 0 rows affected (0.01 sec)
       
      MariaDB [xyz]> select create_time from information_schema.tables
          -> where table_schema='xyz' and table_name='ct_test'\G
      *************************** 1. row ***************************
      create_time: 2015-10-13 17:36:57
      1 row in set (0.00 sec)
       
      MariaDB [xyz]> drop table ct_test;
      Query OK, 0 rows affected (0.01 sec)
       
      MariaDB [xyz]> select now()\g
      +---------------------+
      | now()               |
      +---------------------+
      | 2015-10-13 17:38:14 |
      +---------------------+
      1 row in set (0.00 sec)
       
      MariaDB [xyz]> create table ct_test(id int);
      Query OK, 0 rows affected (0.01 sec)
       
      MariaDB [xyz]> select create_time from information_schema.tables
          -> where table_schema='xyz' and table_name='ct_test'\G
      *************************** 1. row ***************************
      create_time: 2015-10-13 17:38:32
      1 row in set (0.00 sec)
       
      MariaDB [xyz]> drop table ct_test;
      Query OK, 0 rows affected (0.01 sec)
       
      MariaDB [xyz]> select now()\G
      *************************** 1. row ***************************
      now(): 2015-10-13 17:39:24
      1 row in set (0.00 sec)
       
      MariaDB [xyz]> create table ct_test(id int);
      Query OK, 0 rows affected (0.01 sec)
       
      MariaDB [xyz]> select create_time from information_schema.tables
          -> where table_schema='xyz' and table_name='ct_test'\G
      *************************** 1. row ***************************
      create_time: 2015-10-13 17:38:32
      1 row in set (0.00 sec)
       
      MariaDB [xyz]>

      In this example the first drop and recreate worked, but the second did not.
      Sometimes doing a 'optimize table' will cause an update, but not always.

      This might be related to this bug https://bugs.mysql.com/bug.php?id=69689 which is a duplicate of this bug https://bugs.mysql.com/bug.php?id=14374
      It might also be related this this bug https://bugs.mysql.com/bug.php?id=69990 but partitioned tables are not involved here.

      Attachments

        Activity

          People

            wlad Vladislav Vaintroub
            Tuco Tuco
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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