You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BUG#16373054 - CRASH WHEN MYSQL.PROC HAS NO AVAILABLE PK
Analysis
--------
'mysqld' crashes when:
a) The primary key for the system table 'proc' is dropped and
b) A stored procedure is invoked.
Ideally it is expected that system tables are not tampered.
When we access these tables for performing some operation,
we do not check if a valid key information is available.
Since the primary key is dropped, the mysqld crashes while trying
to access the key information. This behavior is observed with
other system tables(user, columns_priv, event and plugin)
as well when it's primary key is dropped. This issue is addressed
with this patch.
Fix:
---
Make sure that key information is available when the operations
accessing the system tables are invoked. In such a case, we now
report an error instead of a crash.
Note: We do not validate complete key information as it could
impact performance. Once MySQL roles is introduced, such checks
would become unnecessary.
eng "STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete."
7084
7084
7085
+
ER_TABLE_CORRUPT
7086
+
eng "Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data."
0 commit comments