database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-08-05 13:16:09 +03:00
Code Activity

MDEV-35039 Number of indexes inside InnoDB differs from that defined in MariaDB after altering table with vector key

Browse Source 
don't show table->s->total_keys to engine in inplace alter
This commit is contained in:
Sergei Golubchik
2024-09-28 23:07:48 +02:00
parent 8253650aaa
commit 0bd01f4a95
3 changed files with 33 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
sql/sql_table.cc
View File

@@ -7319,10 +7319,17 @@ static bool fill_alter_inplace_info(THD *thd, TABLE *table,
Adding/dropping any indexes in a table that already has high-level indexes
may shift high-level indexes numbers. And thus require high-level indexes
rename, which algorithm=inplace (storage engines) shouldn't do.
If we aren't adding/dropping indexes, ha_alter_info->key_count is
table->s->total_keys, but must be table->s->keys to not confuse the engine.
*/
if (table->s->hlindexes() &&
(ha_alter_info->index_drop_count || ha_alter_info->index_add_count))
ha_alter_info->inplace_supported= HA_ALTER_INPLACE_NOT_SUPPORTED;
if (table->s->hlindexes())
{
if (ha_alter_info->index_drop_count || ha_alter_info->index_add_count)
ha_alter_info->inplace_supported= HA_ALTER_INPLACE_NOT_SUPPORTED;
else
ha_alter_info->key_count= table->s->keys;
}
DBUG_PRINT("exit", ("handler_flags: %llu", ha_alter_info->handler_flags));
DBUG_RETURN(false);