[MDEV-26651] Exclude I_S materializtion from updating Created_tmp_tables status counters Created: 2021-09-20 Updated: 2024-01-31 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Hartmut Holzgraefe | Assignee: | Ralf Gebhardt |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Currently during materialization of tables in the information schema, several temporary tables (both in memory and on disk) may be generated, all being counted towards Created_tmp_tables and Created_disk_tmp_tables status counters. E.g. with 10.6.4 right after installation a simple SELECT * FROM INFORMATION_SCHEMA.TABLES; leads to Created_tmp_tables going up by 111, and Created_tmp_disk_tables by 19 With that any checks on these counters don't really make that much sense anymore, especially not the "rate of on-disk tables is too high" checks done by some general monitoring tools like e.g. MonYog ... So my feature request would be to disable updates to these counters for everything that just materializes INFORMATION_SCHEMA data on the fly (and the same for PERFORMANCE_SCHEMA, too, if that's also affected) |