This tool partitions and manages MariaDB tables by sequential IDs.
Note that reorganizing partitions is not a fast operation on ext4 filesystems; it is fast on xfs and zfs. Adding partitions in the first place with InnoDB requires a full table copy.
Similar tools:
- https://github.com/davidburger/gomypartition, intended for tables with date-based partitions
- https://github.com/yahoo/mysql_partition_manager, which is archived and in pure SQL
→ pip install --editable . → partition-manager --log-level=debug \ --mariadb test_tools/fake_mariadb.sh \ add --noop --table tablename DEBUG:root:Auto_Increment column identified as id DEBUG:root:Partition range column identified as id DEBUG:root:Found partition before = (100) DEBUG:root:Found tail partition named p_20201204 INFO:root:No-op mode ALTER TABLE `dbname`.`tablename` REORGANIZE PARTITION `p_20201204` INTO (PARTITION `p_20201204` VALUES LESS THAN (3101009), PARTITION `p_20210122` VALUES LESS THAN MAXVALUE); You can also use a yaml configuration file with the --config parameter of the form:
partitionmanager: dburl: sql://user:password@localhost/db-name # or # mariadb: /usr/local/bin/mariadb partition_duration: days: 7 tables: table1: retention: days: 60 table2: partition_duration: days: 30 table3: retention: days: 14Lots. A drop mechanism, for one. Yet more tests, particularly live integration tests with a test DB, for another.