Bug #67098 performance schema shows stray temporray tables
Submitted: 5 Oct 2012 10:19 Modified: 13 Dec 2012 16:57
Reporter: Sergei Golubchik Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Performance Schema Severity:S3 (Non-critical)
Version:5.6.5, 5.7.0 OS:Any
Assigned to: CPU Architecture:Any

[5 Oct 2012 10:19] Sergei Golubchik
sometimes performance_schema.objects_summary_global_by_type shows tables that were dropped.

How to repeat:
Add to the perfschema.misc test the "--source include/have_innodb.inc" line. It's to prevent mtr from restarting the server. Run

./mtr --verbose-restart --no-reorder flush_read_lock perfschema.misc

Observe the failure.
Additionally, remove "include/haven_innodb.inc" again, run the command as above, and observe how mysqld restart hides the error.
[12 Oct 2012 18:25] Sveta Smirnova
Thank you for the report.

Verified as described.
[13 Dec 2012 16:57] Paul DuBois
Noted in 5.6.10, 5.7.1 changelogs.

The Performance Schema normally ignores temporary table events, but
sometimes failed to properly identify a table as temporary and
consequently recorded events for the table.