[MDEV-15061] TRUNCATE TABLE should honor InnoDB table locks - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Fix Version/s: 10.3.5
Component/s: Storage Engine - InnoDB
Labels:
- consistency
- ddl
- truncate

Description

Traditionally, DROP TABLE and TRUNCATE TABLE discarded any locks that may have been held on the table. This feels like an ACID violation. Probably most occurrences of it were prevented by meta-data locks (MDL) which were introduced in MySQL 5.5.

It is cleaner to always protect DDL operations with an exclusive table lock. Other operations are doing this in MariaDB 10.3, but not TRUNCATE TABLE.

Attachments

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2018-01-25 08:25

Updated:: 2018-02-04 11:11

Resolved:: 2018-01-25 21:50

Git Integration

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