Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
According to MariaDB documentation, this query:
https://mariadb.com/kb/en/innodb-temporary-tablespaces/
SELECT FILE_NAME AS "File Name",
INITIAL_SIZE AS "Initial Size",
DATA_FREE AS "Free Space",
TOTAL_EXTENTS * EXTENT_SIZE AS "Total Size",
MAXIMUM_SIZE AS "Max"
FROM information_Schema.FILES
;
Empty set (0.000 sec)
should show some results when using explicit temporary innodb tables:
create temporary table temp_random (
id bigint primary key,
random decimal not null
) engine = innodb;
insert into temp_random(id, random) select seq, rand() from seq_0_to_2000000;
drop temporary table temp_random;
but does not. Possibly related to: https://jira.mariadb.org/browse/MDEV-26782
Attachments
Issue Links
- relates to
-
MDEV-26782 InnoDB temporary tablespace: reclaiming of free space does not work
-
- Closed
-
-
MDEV-11426 Remove InnoDB INFORMATION_SCHEMA.FILES implementation
-
- Closed
-
-
MDEV-22343 Remove SYS_TABLESPACES and SYS_DATAFILES
-
- Closed
-
I believe that INFORMATION_SCHEMA.FILES never returned anything for InnoDB in MariaDB. In
MDEV-11426the implementation that was added in MySQL 5.7 was intentionally removed. InMDEV-22343(MariaDB 10.6.0) the implementation of INFORMATION_SCHEMA.INNODB_SYS_TABLESPACES and INFORMATION_SCHEMA.INNODB_SYS_DATAFILES was changed to return data straight from the memory. If those views do not cover the InnoDB temporary tablespace, it should be possible to add support (in MariaDB 10.6 or later).In any case, the documentation is wrong if it really says that about INFORMATION_SCHEMA.FILES. It could be that the view always returns the empty result in MariaDB.