Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Starting with MySQL 5.7, temporary tables in InnoDB are handled differently from persistent tables. Because temporary tables are private to a connection, concurrency control and multi-versioning (MVCC) are not applicable. For performance reasons, purge is disabled as well. Rollback is supported for temporary tables.
Because MVCC and purge are disabled for temporary tables, we should discard all temporary undo logs already at transaction commit, just like we discard the persistent insert_undo logs. Currently, update_undo logs are being preserved.
Attachments
Issue Links
- blocks
-
MDEV-12226 Avoid writes of freed (garbage) pages to InnoDB data files
- Closed
- relates to
-
MDEV-12258 InnoDB: Fix the bogus debug assertion introduced in MDEV-12219
- Closed