Bug #107769 | It's wrong when io_cache calculate info->write_end | ||
---|---|---|---|
Submitted: | 6 Jul 2022 8:07 | Modified: | 6 Jul 2022 11:34 |
Reporter: | shang canfang | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | MySQL5.7.26 | OS: | Linux |
Assigned to: | CPU Architecture: | x86 | |
Tags: | io_cache, write |
[6 Jul 2022 8:07]
shang canfang
[6 Jul 2022 11:34]
MySQL Verification Team
Hi Mr. ye, Thank you for your bug report. However, we can not change the manner in which write_end is calculated in our IO_CACHE system. Several of our storage engines and temporary files use this algorithm instead of the simple unbuffered FILE operation. That means that any changes would created huge problems for any upgrade to some newer 5.7 release. Simply, those tables or files would suddenly become unreadable and non-writeable in newer releases. Changes like these can only be done in newer versions, like 8.0, but 8.0 does not use those source files any more. Hence, after 5.7 this code is not used any more ...... Not a bug.