Bug #82752 SHOW TABLE STATUS WHERE `Name` = returns different value after db stop-start

• Submitted: 27 Aug 2016 15:02
• Modified: 28 Aug 2016 12:02
• Reporter: Jacques Valois
• Status: Not a Bug
• Category: MySQL Server: DML
• Severity: S5 (Performance)
• Version: 6.3.7
• OS: Windows (Microsoft Windows 7 Ultimate Service Pack 1)
• CPU Architecture: Any
• Tags: WBBugReporter

[27 Aug 2016 15:02] Jacques Valois

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\Jacques\AppData\Roaming\MySQL\Workbench\log\wb.log]

When using the "SHOW TABLE STATUS WHERE `Name` =" to show the next available sequence for a table, the DML statement will return different values before a stop-start of the db than after the stop-start.

How to repeat:
1-insert 1 row into a table and commit;
2-run the SHOW TABLE STATUS WHERE `Name` = table name (value should be 2)
3-delete row #1 and commit;
4-run again the SHOW TABLE STATUS WHERE `Name` = table name (value should be 2)
5-stop database
6-start database
7-run again the SHOW TABLE STATUS WHERE `Name` = table name (value should be 1)

[27 Aug 2016 15:03] Jacques Valois

Requested log file

Attachment: wb.log (application/octet-stream, text), 108.62 KiB.

[27 Aug 2016 17:18] MySQL Verification Team

It sounds like the expected behavior of innodb auto_increment handling.  Please confirm.

http://dev.mysql.com/doc/refman/5.7/en/innodb-auto-increment-handling.html
"InnoDB AUTO_INCREMENT Counter Initialization"

[28 Aug 2016 12:02] Jacques Valois

This appears to be a normal behavior for InnoDB.

Regards,