[MDEV-11335] Changing delay_key_write option for MyISAM table should not copy rows - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 5.5(EOL), 10.0(EOL), 10.1(EOL)
Fix Version/s: 10.1.24, 10.2.7
Component/s: Data Definition - Alter Table, Storage Engine - MyISAM
Labels:
- MyISAM
- upstream

Description

Currently, changing delay_key_write option for MyISAM table using ALTER TABLE statement copies all table rows to a temporary table during alteration. However, it is totally unnecessary. Changing this attribute should not copy rows.

One can just create a table with the same structure and this option set and then copy/rename .frm file, but why to rely on workaround when this can be implemented by server itself?

See https://bugs.mysql.com/bug.php?id=45492 upstream MySQL bug also.

Attachments

Issue Links

relates to

MDEV-12836 Avoid table rebuild when removing of auto_increment settings

Closed

MDEV-13636 ALTER TABLE ... DELAY_KEY_WRITE=1 creates table copy for MyISAM table with DATA DIRECTORY/INDEX DIRECTORY options

Closed

links to

Bug #45492 changing delay_key_write option should not copy rows

Activity

Sergei Golubchik added a comment - 2017-01-16 18:57

This is a bit tricky. delay_key_write option is stored in the MYI file and MyISAM does not support rewriting MYI header only, it has to recreate the whole MYI file.

Sergei Golubchik added a comment - 2017-01-16 18:57 This is a bit tricky. delay_key_write option is stored in the MYI file and MyISAM does not support rewriting MYI header only, it has to recreate the whole MYI file.

People

Assignee:: Sergei Golubchik

Reporter:: Valerii Kravchuk

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2016-11-22 16:51

Updated:: 2024-07-08 01:11

Resolved:: 2017-05-24 12:04

Git Integration

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

MariaDB Server