fdatasync() can be used for transaction log and doublewrite buffer
Bug #803270 reported by
Yasufumi Kinoshita
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Unassigned | ||
| 5.1 |
Fix Released
|
Medium
|
Unassigned | ||
| 5.5 |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
fsync() is intended to sync also metadata of the file (size, name, access time, etc..)
But sync for transaction log and doublewrite buffer don't need to change such metadata of the each files.
From point of view about performance, fdatasync() is better for them than fsync().
Related branches
lp:~percona-dev/percona-server/5.1.57-803270-fdatasync
- Stewart Smith: Pending requested
-
Diff: 950 lines (+330/-69)7 files modifiedinnodb_bug60788.patch (+8/-8)
innodb_extend_slow.patch (+13/-13)
innodb_fix_misc.patch (+18/-18)
innodb_io_patches.patch (+285/-24)
innodb_pass_corrupt_table.patch (+2/-2)
innodb_recovery_patches.patch (+1/-1)
innodb_separate_doublewrite.patch (+3/-3)
lp:~percona-dev/percona-server/5.5.13-803270-fdatasync
- Stewart Smith: Pending requested
-
Diff: 790 lines (+361/-45)7 files modifiedinnodb_bug60788.patch (+8/-8)
innodb_extend_slow.patch (+12/-12)
innodb_fix_misc.patch (+15/-15)
innodb_io_patches.patch (+320/-4)
innodb_pass_corrupt_table.patch (+2/-2)
innodb_recovery_patches.patch (+1/-1)
innodb_separate_doublewrite.patch (+3/-3)
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/