Richard DEMONGEOT added a comment - 2022-05-12 07:53 - edited Works after an alter table on InnoDB Works also if alter back into MyISAM. Works also if - starting from the snapshot - alter table engine=MyISAM In all cases : MariaDB [DATA_V3] > show table status like 'EDA_SITE_RESULT_REAL_TIME' \G Name: EDA_SITE_RESULT_REAL_TIME Engine: MyISAM Version: 10 Row_format: Fixed Collation: utf8mb3_general_ci Checksum: NULL Create_options: partitioned Temporary: N

VAROQUI Stephane added a comment - 2022-05-12 08:16 Looks like altering back to MyISAM is fixing the issue

Richard DEMONGEOT added a comment - 2022-05-12 10:39 - edited Even with truncated tables it fails. (empty but comes from an old version) Before to alter table : MariaDB [information_schema]> select * from TABLES WHERE TABLE_SCHEMA='DATA_V3' \G *************************** 1. row *************************** TABLE_CATALOG: def TABLE_SCHEMA: DATA_V3 TABLE_NAME: EDA_SITE_RESULT_REAL_TIME TABLE_TYPE: BASE TABLE ENGINE: MyISAM VERSION: 10 ROW_FORMAT: Fixed TABLE_ROWS: 0 AVG_ROW_LENGTH: 0 DATA_LENGTH: 0 MAX_DATA_LENGTH: 0 INDEX_LENGTH: 13312 DATA_FREE: 0 AUTO_INCREMENT: 1 CREATE_TIME: 2022-02-18 01:21:02 UPDATE_TIME: 2022-05-12 12:36:38 CHECK_TIME: 2022-05-12 01:06:03 TABLE_COLLATION: utf8mb3_general_ci CHECKSUM: NULL CREATE_OPTIONS: partitioned TABLE_COMMENT: MAX_INDEX_LENGTH: 0 TEMPORARY: N After the add partition TABLE_CATALOG: def TABLE_SCHEMA: DATA_V3 TABLE_NAME: EDA_SITE_RESULT_REAL_TIME TABLE_TYPE: BASE TABLE ENGINE: NULL VERSION: NULL ROW_FORMAT: NULL TABLE_ROWS: NULL AVG_ROW_LENGTH: NULL DATA_LENGTH: NULL MAX_DATA_LENGTH: NULL INDEX_LENGTH: NULL DATA_FREE: NULL AUTO_INCREMENT: NULL CREATE_TIME: NULL UPDATE_TIME: NULL CHECK_TIME: NULL TABLE_COLLATION: NULL CHECKSUM: NULL CREATE_OPTIONS: NULL TABLE_COMMENT: Got error 190 "Incompatible key or row definition between the MariaDB .frm file and the information in the storage engine. You may have retry " from storage engine MyISAM MAX_INDEX_LENGTH: NULL TEMPORARY: NULL Edit : Current 10.3 (corrupted?) empty tables/partitions are uploaded into file table-sample.tgz. Last created partition : p20220515 Next day should be : ALTER TABLE DATA_V3.EDA_SITE_RESULT_REAL_TIME REORGANIZE PARTITION pDEFAULT INTO ( PARTITION p20220516 VALUES LESS THAN ( UNIX_TIMESTAMP( '2022-05-17')), PARTITION pDEFAULT VALUES LESS THAN MAXVALUE)

Elena Stepanova added a comment - 2022-07-25 22:32 --source include/have_partition.inc   SET GLOBAL mysql56_temporal_format= OFF ;   CREATE TABLE t (ts timestamp , KEY (ts)) ENGINE=MyISAM PARTITION BY RANGE (unix_timestamp(ts)) ( PARTITION p1 VALUES LESS THAN (1645398000), PARTITION pn VALUES LESS THAN MAXVALUE ); SET GLOBAL mysql56_temporal_format= ON ; FLUSH TABLES; ALTER TABLE t DROP PARTITION p1; CHECK TABLE t;   # Cleanup DROP TABLE t; 10.4 8911823f ALTER TABLE t DROP PARTITION p1; CHECK TABLE t; Table Op Msg_type Msg_text test.t check Error Got error 190 "Incompatible key or row definition between the MariaDB .frm file and the information in the storage engine. You have to dump an" from storage engine MyISAM test.t check error Corrupt DROP TABLE t;

Alexander Barkov added a comment - 2022-10-25 08:12 - edited Hello serg , can you please review a patch: https://github.com/MariaDB/server/commit/b2800c06b22832b976cc05c142d00109ddaa1ba7 ? Thanks!