Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5
Description
MDEV-14717 made rename operations inside InnoDB transactional and crash-safe in case the server process is killed.
However, the file-renaming operations might not be carried out in a fashion that guarantees crash-safety in a case that involves file system recovery.
To be safe, we should probably do fsync() of the file and the directory containing it, followed by the rename(), and finally an fsync() of the file and of its containing directory. This should be done both inside storage engines and in code that deals with .frm files and the like.
Attachments
Issue Links
- relates to
-
MDEV-14717 RENAME TABLE in InnoDB is not crash-safe
- Closed