[MDEV-31708] InnoDB and catalogs Created: 2023-07-15  Updated: 2023-12-22

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 11.5

Type: Task Priority: Major
Reporter: Michael Widenius Assignee: Michael Widenius
Resolution: Unresolved Votes: 1
Labels: None

Issue Links:
PartOf
is part of MDEV-31542 Add multi-tenancy catalogs to MariaDB Stalled

 Description   
  • Review InnoDB changes in catalog tree
  • Use catalog version of innodb_index_stats and innodb_table_stats.
    • No catalog name are stored in these as these should be catalog specific.
  • Move --innodb-sys-foreign[=name], innodb-sys-foreign-cols=[name] and
    other innodb-sys tables to be catalog specific (if possible and if it makes sense).
  • Add catalog column to Innodb sys tables -> Catalog related sys tables (like index_stats, table_stats, should be per catalog)
  • Add catalog column to innodb_cmp_per_index table
    • Check innobase/handler/i_s.cc and ensure that all fix_name() calls has also have corresponding calls to stores the catalog in the table. fix_name() is used to remove the catalog from a database or table name.
  • select * from innodb_sys_foreign, innodb_sys_table_spaces and other sys tables should only show tables from current catalog.
    • add 'where catalog_name=catalog()' to the WHERE clause
  • Ensure that innodb_ft_server_stopword_table uses the current catalog.
    • filename should be stored in SQL_CATALOG!
  • Ensure that innodb_ft_server_stopword_table uses the current catalog
    • filename should be stored in current SQL_CATALOG so that each user can
      use different filenames.

Generated at Thu Feb 08 10:25:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.