Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5, 10.6
-
None
-
None
Description
The likehood of mysql.proc being corrupted because of the errors it gets are unlikely. Its usually got a fixable structure with mariadb-upgrade.
mysq.proc in overriding the function "Table_check_intact_log_error::report_error" creates the excessive potential corruption warnings.
The calls to report_error in sql/table.cc, verifing the system table structures, call report error with
- ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE
- ER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2 (when the versions of table and server are the same)
- 0 - for when datatypes in table don't match
- 0 - for missing /incorrect primary or secondary keys
For the mysql.proc table everything non-0 is mapped to ER_CANNOT_LOAD_FROM_TABLE_V2
Attachments
Issue Links
- relates to
-
MDEV-27517 mariadb-upgrade from MySQL 5.7 pollutes stdout on some sys schema views
- Open
-
MDEV-28765 Drop database warnings
- Open
-
MDEV-29648 Dump upgrade from pre-10.6 to 10.6+ throws errors on sys views
- Open
- links to