| Bug #51396 | about the bufferts | ||
|---|---|---|---|
| Submitted: | 22 Feb 2010 17:18 | Modified: | 22 Feb 2010 17:33 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: MyISAM storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.0.90, 5.1.44, 5.5.99-m3 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | typo | ||
[22 Feb 2010 17:33]
MySQL Verification Team
another one in records.cc:
DBUG_PRINT("info",("Allocated buffert for %d records",info->cache_records));
[22 Feb 2010 17:33]
Valeriy Kravchuk
Thank you for the bug report. Verified just as described: 77-52-24-143:mysql-5.1 openxs$ grep -rn bufferts * sql/sql_load.cc:29: *end_of_buff; /* Data in bufferts ends here */ storage/myisam/mi_check.c:1918: mi_check_print_error(param,"%d when trying to write bufferts",my_errno);

Description: two typos where 'bufferts' is used incorrectly: 1) in flush_blocks function in mi_check.cc we have this line: mi_check_print_error(param,"%d when trying to write bufferts",my_errno); 2) in class READ_INFO { definition in sql_load.cc there's a comment: *end_of_buff; /* Data in bufferts ends here */ How to repeat: grep source for bufferts Suggested fix: s/bufferts/buffers/