Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4.14
-
None
-
CentOS Linux release 7.8.2003 (Core)
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`
Attachments
Issue Links
- duplicates
-
MDEV-15951 system versioning by trx id doesn't work with partitioning
- Closed
- relates to
-
MDEV-20271 Partitioned versioned tables do not accept Trx IDs
- Open
-
MDEV-25173 paritioning not supported on transaction-precise versioned tabled
- Open