Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL)
Description
It appears that innodb_safe_truncate makes TRUNCATE unsafe:
--source include/have_innodb.inc
|
|
CREATE TEMPORARY TABLE t1 (a INT) ENGINE=InnoDB; |
ALTER TABLE t1 ENCRYPTED=NO; |
TRUNCATE t1; |
10.2 861038f2e with default innodb_safe_truncate=ON |
CURRENT_TEST: bug.temp3
|
mysqltest: At line 5: query 'TRUNCATE t1' failed: 1030: Got error 140 "Wrong create options" from storage engine InnoDB
|
2018-12-01 13:41:46 140647973488384 [Warning] Could not remove temporary table: '/data/bld/10.2/mysql-test/var/tmp/mysqld.1/#sql769d_9_1', error: 2
|
There is no warning/error with innodb_safe_truncate=OFF
Attachments
Issue Links
- is caused by
-
MDEV-13564 TRUNCATE TABLE and undo tablespace truncation are not compatible with Mariabackup
- Closed
- relates to
-
MDEV-17816 InnoDB: Failing assertion: trx->dict_operation_lock_mode == RW_X_LATCH upon TRUNCATE TABLE after converting to REDUNDANT
- Closed
-
MDEV-17833 ALTER TABLE is not enforcing prefix index size limit
- Closed
-
MDEV-17983 CREATE TEMPORARY TABLE is inconsistent when refusing InnoDB table options
- Open