diff options
| author | Sergey Vojtovich <sergey.vojtovich@oracle.com> | 2011-10-20 15:03:22 +0400 |
|---|---|---|
| committer | Sergey Vojtovich <sergey.vojtovich@oracle.com> | 2011-10-20 15:03:22 +0400 |
| commit | de8c70e70b3fd335e1d34a5635fc4357adb43d95 (patch) | |
| tree | 4e8a0018a765d64da5e5172478b8d28e2435b69f /cmd-line-utils/libedit/sys.h | |
| parent | fd955448c86018539e1e46a7390273dff11f0291 (diff) | |
| download | mariadb-git-de8c70e70b3fd335e1d34a5635fc4357adb43d95.tar.gz | |
BUG#11757032 - 49030: OPTIMIZE TABLE BREAKS MYISAM TABLE WHEN
USING MYISAM_USE_MMAP ON WINDOWS
When OPTIMIZE/REPAIR TABLE is switching to new data file,
old data file is removed while memory mapping is still
active.
With 5.1 implementation of nt_share_delete() it is not
permitted to remove mmaped file.
This fix disables memory mapping for mi_repair() operations.
mysql-test/r/myisam.result:
A test case for BUG#11757032.
mysql-test/t/myisam.test:
A test case for BUG#11757032.
storage/myisam/ha_myisam.cc:
mi_repair*() functions family use file I/O even if memory
mapping is available.
Since mixing mmap I/O and file I/O may cause various artifacts,
memory mapping must be disabled.
storage/myisam/mi_delete_all.c:
Clean-up: do not attempt to remap file after truncate, since
there is nothing to map.
Diffstat (limited to 'cmd-line-utils/libedit/sys.h')
0 files changed, 0 insertions, 0 deletions