[MDEV-23773] Cannot store the history separately for the transaction precise history tables. Created: 2020-09-21  Updated: 2021-03-30

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.4.14
Fix Version/s: 10.4, 10.5

Type: Bug Priority: Major
Reporter: YURII KANTONISTOV Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Environment:

CentOS Linux release 7.8.2003 (Core)


Issue Links:
Duplicate
duplicates MDEV-15951 system versioning by trx id doesn't w... Closed
Relates
relates to MDEV-20271 Partitioned versioned tables do not a... Open
relates to MDEV-25173 paritioning not supported on transac... Open

 Description   

For the tables with transaction precise history cannot put history data into own partition(s).

Meaning the maintenance and cleanup of the huge tables is unefficient and very heavy task.

Meaning in turn transaction precise history is not really usable feature for production environment:

MariaDB [db]> CREATE TABLE t(
-> x INT,
-> start_trxid BIGINT UNSIGNED GENERATED ALWAYS AS ROW START,
-> end_trxid BIGINT UNSIGNED GENERATED ALWAYS AS ROW END,
-> PERIOD FOR SYSTEM_TIME(start_trxid, end_trxid)
-> ) WITH SYSTEM VERSIONING
-> PARTITION BY SYSTEM_TIME LIMIT 100000 (
-> PARTITION p_hist HISTORY,
-> PARTITION p_cur CURRENT
-> );
ERROR 4110 (HY000): `start_trxid` must be of type TIMESTAMP(6) for system-versioned table `t`


Generated at Thu Feb 08 09:24:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.