mirror of
https://github.com/MariaDB/server.git
synced 2025-07-29 05:21:33 +03:00
MDEV-24758 heap-use-after-poison in innobase_add_instant_try/rec_copy
This is a backport of commitfd9ca2a742
(MDEV-23295) and commit9a156e1a23
(MDEV-23345) to 10.3. An instant ADD/DROP/reorder column could create a dummy table object with the wrong ROW_FORMAT when innodb_default_row_format was changed between CREATE TABLE and ALTER TABLE. prepare_inplace_alter_table_dict(): If we had promised that ALGORITHM=INPLACE is supported, we must preserve the ROW_FORMAT. The rest of the changes are related to adding Alter_inplace_info::inplace_supported to cache the return value of handler::check_if_supported_inplace_alter().
This commit is contained in:
@ -2347,6 +2347,9 @@ public:
|
||||
/** true for online operation (LOCK=NONE) */
|
||||
bool online;
|
||||
|
||||
/** which ALGORITHM and LOCK are supported by the storage engine */
|
||||
enum_alter_inplace_result inplace_supported;
|
||||
|
||||
/**
|
||||
Can be set by handler to describe why a given operation cannot be done
|
||||
in-place (HA_ALTER_INPLACE_NOT_SUPPORTED) or why it cannot be done
|
||||
|
Reference in New Issue
Block a user