[MDEV-30065] "mariadb-install-db --enforce-storage-engine=InnoDB" fails with InnoDB errors Created: 2022-11-21 Updated: 2023-07-04 |
|
| Status: | Stalled |
| Project: | MariaDB Server |
| Component/s: | Locking |
| Affects Version/s: | 10.5 |
| Fix Version/s: | 10.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Black | Assignee: | Daniel Black |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | not-10.3 | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Description |
|
It should be possible to create InnoDB system tables. This gives uses the option for [smaller backups](https://stackoverflow.com/questions/74511347/mariadb-incremental-backup-generates-large-files-for-unchanged-database), and like Azure, to use InnoDB only.
Could remove the InnoDB error in bootstrap. But otherwise works.
10.5+ is a FK sql fix. + once resolved, ER_WRONG_LOCK_OF_SYSTEM_TABLE is triggered for the LOCK TABLES in the scripts/fill_help_tables.sql.
|
| Comments |
| Comment by Daniel Black [ 2022-11-22 ] |
|
10.5: prepare_fk_prelocking_list - adds FK tables referenced in the lock list, to the locking list at TL_READ By the time lock_tables_check is called its indistinguishable between lock tables help_topic write, help_category write and lock tables help_topic write, help_category write, help_relations read In 10.4, table->file->referenced_by_foreign_key(), in DML_prelocking_strategy::handle_table (called from Lock_tables_prelocking_strategy::handle_table) returns false. |
| Comment by Daniel Black [ 2022-11-23 ] |
|
serg, looked at the locking far too much. I put something easy in PR 2342 that relaxes the ER_WRONG_LOCK_OF_SYSTEM_TABLE by a minimal amount. I couldn't differentiate a FK table lock and a normal lock without restructuring a few layers. |
| Comment by Daniel Black [ 2022-12-19 ] |
|
|